AFAS invoicing: invoice modes and payment bookings
In the AFAS integration, the invoice document and the payment booking are two separate flows, each with its own trigger and connector. An environment can therefore create a real sales invoice and book the iDEAL down-payment as a financial entry — the two do not conflict.
1. Invoice modes
The invoice mode determines which UpdateConnector is used and what appears in AFAS:
| Invoice mode | UpdateConnector | Result in AFAS |
|---|---|---|
| Financial entry incl. VAT (default) | FiEntries | Journal entry (debit/credit lines); AFAS calculates the VAT. |
| Financial entry excl. VAT | FiEntries | Same journal entry, lines based on amounts excl. VAT. |
| Sales invoice | KnSalesInvoice or FiInvoice | A real sales invoice document. |
| Direct invoice | FbDirectInvoice | Native sales invoice with article lines. |
| Direct mutations | FBDirectMutations | Financial entry with manual VAT control. |
2. Missing connectors are not blockers
During onboarding, AFAS administrators sometimes report that KnSalesInvoice or FBDirectMutations does not exist in their environment. That is not a problem — the connectors per mode are alternatives, not a combined hard requirement:
KnSalesInvoicemissing → useFiInvoiceas the invoice connector within the same sales-invoice mode. The integration then automatically switches the line object (fromKnSalesInvoiceLinetoFiInvoiceLine).FBDirectMutationsmissing → not needed; the default route for financial entries isFiEntries, with the same bookkeeping result (AFAS calculates the VAT).
3. Which mode should you choose?
| Goal in AFAS | Mode | Required connector(s) |
|---|---|---|
| Only financial bookings (no invoice document) | Financial entry | FiEntries |
| A real sales invoice document | Sales invoice (with FiInvoice) | FiInvoice + FiEntries (payments) |
In both cases, the debtor connector is also required, plus read rights on VAT codes, ledger accounts, cost centres and journals — see Setting up AFAS Profit.
4. Payment booking (down-payments)
As soon as a payment (iDEAL, credit card, bank) reaches the status paid, the integration books it as a two-line journal entry through FiEntries: bank (debit) against debtor (credit). This always goes through FiEntries, regardless of the chosen invoice mode. If the payment came in before the invoice was finalised, it is booked retroactively.
The debtor line carries the invoice number, so AFAS auto-matches the payment against the open item. The rest of the debtor follow-up (open balance, dunning) then continues in AFAS itself.
Note: the payment booking requires both the payment journal (journal code) and the bank/clearing account (ledger account) to be set in the integration. If either is missing, the booking is silently skipped — the down-payment will never reach AFAS.
5. External invoice number (optional)
By default, i-Reserve assigns the invoice number. Optionally the integration can push the invoice to AFAS first and use the number assigned by AFAS as the invoice number in i-Reserve. This only works in the sales invoice and direct invoice modes — a financial entry has no invoice document.
