Vendor Payment Advice Email Program
Short answer: A custom program that, after an automatic payment run, emails every vendor a PDF payment advice listing the invoices that were paid. A preview comes first, and the sending result is logged per vendor.
- Estimated effort
- M · 4–7 working days
- System
- ECC and S/4HANA
- Tables
- 5
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
F110 produces the payment advice through printing or standard output management; the advice form, the choice of the recipient email address and bulk sending as PDF have to be set up per company. Several email addresses, copy recipients and a resend check are not part of the standard flow. To cut vendor queries, an automatic email on the payment day is needed.
Who uses it? Accounts payable teams and finance teams that answer vendors' "which of my invoices did you pay" questions.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| REGUHPayment Program Settlement Data | Payment document, payee, payment amount and currency (driving table) | Read | ECC + S/4 |
| REGUPPayment Program Processed Items | Paid invoices, reference and cash discount | Read | ECC + S/4 |
| LFB1Vendor Master (Company Code) | Accounting email address in the company code | Read | ECC + S/4 |
| LFA1Vendor Master (General Section) | Vendor address number | Read | ECC + S/4 |
| ADR6E-Mail Addresses (Business Address Services) | Default email in the vendor address | Read | ECC + S/4 |
BAPIs and functions used
- SO_NEW_DOCUMENT_ATT_SEND_API1SAPoffice: Send New Document with Attachments. Sends the payment advice by email as a PDF attachment
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_LAUFD | Run date | Single value | REGUH-LAUFD | Yes | 17.11.2026 |
| P_LAUFI | Run identification | Single value | REGUH-LAUFI | Yes | HAFT1 |
| S_ZBUKR | Paying company code | Range / multiple | REGUH-ZBUKR | No | 1000 |
| S_LIFNR | Vendor | Range / multiple | REGUH-LIFNR | No | 100245 |
| P_CC | Copy recipient email | Single value | — | No | [email protected] |
| P_TEST | Test mode (preview only) | Checkbox | — | No | X |
| P_RESEND | Resend advices already sent | Checkbox | — | No | — |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Vendor | REGUH-LIFNR |
| 2 | Vendor name | REGUH-NAME1 |
| 3 | Payment document | REGUH-VBLNR |
| 4 | Payment amount | REGUH-RBETR |
| 5 | Currency | REGUH-WAERS |
| 6 | Invoice count | Calculated Number of REGUP rows for the payment document |
| 7 | ADR6-SMTP_ADDR | |
| 8 | Status | Calculated Sent, preview, no address or error |
| 9 | Message | Calculated Return message of the send function |
Sample result list
| Vendor | Vendor name | Payment document | Payment amount | Currency | Invoice count | Status | Message | |
|---|---|---|---|---|---|---|---|---|
| 100245 | Atlas Ambalaj | 2000018841 | 171,200 | TRY | 2 | [email protected] | Sent | Email queued for sending |
| 100387 | Delta Metal | 2000018842 | 48,960 | TRY | 1 | [email protected] | Sent | Email queued for sending |
| 100512 | Ege Kimya | 2000018843 | 25,560 | TRY | 1 | No address | LFB1-INTAD and address email are empty |
How does the program work?
- The actual payment records of the selected run are read: REGUH with XVORL blank and the payment document (VBLNR) filled.
- For every payment document the paid invoices come from REGUP: reference (XBLNR), document date, gross amount, cash discount (SKNTO) and net payment.
- The recipient address is determined: first LFB1-INTAD (accounting email in the company code), otherwise the default email of the vendor address (LFA1-ADRNR → ADR6-SMTP_ADDR, FLGDEFAULT).
- The advice form (Smart Form or Adobe Form) is converted to PDF; in test mode only a preview is shown.
- In a real run the PDF is sent as an attachment with SO_NEW_DOCUMENT_ATT_SEND_API1; vendors without an address and errors are listed in the log, and unless P_RESEND is set, payment documents already sent are skipped.
Performance notes
Read REGUH/REGUP by the run key and collect addresses in one pass. For runs with hundreds of vendors, schedule the program as a background job after the payment run; the send queue is monitored in SOST.
Features
- Test mode (check without posting) Each vendor's advice can be previewed before sending.
- Line-by-line result and error log
- Runs as a background job Can start automatically in a job chain after the payment run.
- Send the result by email
Authorization objects
- F_REGU_BUKAccess to payment program data by company code
- F_LFA1_BUKVendor master authorization by company code
- S_OC_SENDAuthorization to send external email from SAP
Frequently asked questions
Can one vendor receive it at several addresses?
Yes. All emails in the address or only the default one can be chosen; P_CC adds a fixed copy recipient to every email.
Can the advice layout be changed?
The form is designed per company: logo, bank details, invoice reference and deduction lines can be added. The Turkish or English version is chosen by the vendor's language.
Can the same advice be sent twice?
Sent payment documents are logged and skipped in the next run. If the vendor asks again, it is resent with P_RESEND.
Related reports
Customer Account Statement and Balance Confirmation Email Program
A custom program that prepares a customer account statement as PDF, with opening balance, period movements, open items and closing balance, and sends …
Payment Proposal Exceptions and Blocked Items Report
A custom report that collects, in one ALV list, the items in an automatic payment program (F110) proposal that will not be paid and the vendor items …
Let us build this program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.