Key Takeaways
- A clearing instruction carries eight fields, from the entity to a unique reference that makes a retry safe.
- Among end users of the cash application software The Hackett Group assessed, the median auto-match rate is 70% (The Hackett Group, 2025).
- Eight exceptions stop or change a posting; each needs a written rule, signed off by the controller, before go-live.
- The ERP stays the system of record and runs its own period, account and tolerance checks again at posting.
- Transformance posts, clears and writes journal entries back, with the method chosen for your requirements; the ERP connection typically takes 2-3 days.
In This Article
- Key Takeaways
- How does an external system post a payment and clear open items?
- What does a clearing instruction have to contain?
- How does each ERP record a payment against open items?
- What happens when a payment does not match its open items exactly?
- Which exceptions stop a posting, and what should the sender do?
- What happens to payments that arrive in a locked or closed period?
- How do you correct a wrong clearing or posting?
- How does Transformance post payments and clear open items in your ERP?
How does an external system post a payment and clear open items?
An external system sends the ERP one instruction per payment: which open items it clears, how much per item and where any difference goes; the ERP validates it and posts.
How a payment from an external system becomes a clearing in the ERP
Clearing is the ERP posting that assigns a payment to open items so that their balance is zero. In SAP S/4HANA, the system clears open items with a zero balance, “changes their status to Cleared, and creates a clearing journal entry”; each cleared item carries that entry’s number and the clearing date (SAP Learning, receivables course).
The exception path decides the result. Among end users of the cash application software assessed by The Hackett Group (2025), the median auto-match rate is 70%, and a third exceed 80%. Every payment that does not match automatically reaches a person. For the far end of the scale, see touchless cash application.
SAP itself notes that “it is not always possible to clear an open item automatically during incoming payment processing”; in its example, the automatic job stops on differing reference information (SAP Learning). That gap is the case an external system is built for. And whatever the sender checked, the ERP checks again.
What does a clearing instruction have to contain?
A clearing instruction names the entity, customer account, payment amount, currency and dates, every open item with its amount, how to treat any difference and why, and a unique reference.
Eight fields every clearing instruction carries
- Entity: company code, legal entity, subsidiary or business unit.
- Customer account, plus the payer if a parent company pays for a subsidiary.
- Payment amount and currency, as on the bank statement.
- Value date (when the cash arrived) and posting date (an open period); never move the value date to fit a period.
- Every open item to clear, with the amount applied to each.
- Difference treatment: partial payment, residual item, tolerance posting or on account, with a reason code.
- Bank account or clearing account the payment posts to.
- A unique reference (bank statement line or payment ID), so a retry cannot post twice.
Entity first. Open items, periods and blocks are kept per entity: the company code in SAP, the legal entity in Dynamics 365 Finance & Operations, the subsidiary in NetSuite OneWorld, the business unit in Oracle. One transfer for two entities needs one posting per entity (multi-entity order-to-cash).
The amount per item is the instruction. “Clear invoice 4711” without an amount lets the ERP decide what happens to a difference. After a timeout, the sender checks whether the reference already posted before it resends. The full field map: what data AR automation reads from and writes to the ERP.
How does each ERP record a payment against open items?
Each ERP has its own clearing object: SAP creates a clearing document, Dynamics 365 settles transactions, Business Central applies ledger entries, NetSuite and Oracle apply payments, Odoo reconciles.
- SAP S/4HANA and ECC. “A clearing transaction always creates a clearing document”, and “an incoming payment, which is used in accounts receivable, clears an open debit amount” (SAP Learning, S/4HANA course). Clearing runs per company code. SAP’s own matching is covered in the SAP cash application guide.
- Dynamics 365 Finance & Operations. “Settlement is the process of settling an invoice against a payment or credit note.” With Automatic settlement set to Yes, a transaction settles against open transactions when it posts; with No, users settle on the Settle transactions page (Microsoft Learn, 2026).
- Business Central. You “apply the payment to one or more debit entries when you post the payment”, or later from the posted entries, partial amounts included (Microsoft Learn, 2025).
- Oracle and NetSuite. Oracle documents for E-Business Suite that a receipt can be applied partially or fully to one or several debit items; the rest stays unapplied or goes on account (Oracle, Release 12.1). In NetSuite, a customer payment is applied to invoices, and the rest stays unapplied (AI agents for Oracle and NetSuite AR).
- Odoo. Registering a payment “generates a new journal entry”; the invoice shows In payment until it is reconciled with a bank transaction, then Paid (Odoo, 18.0 documentation).
Each vendor documents several inbound routes (bank statement import, lockbox files, payment journals, APIs, file upload); which one fits is a decision for your ERP team.
What happens when a payment does not match its open items exactly?
A payment that differs from its open items ends as a partial payment, a residual item, a tolerance posting or an amount on account, depending on tolerances and the instruction.
SAP names its two manual methods plainly (SAP Learning, S/4HANA course). Partial payment: “All the documents remain in the account as open items.” Residual item: “The original document and the payment are cleared”, and only the residual remains. Reason codes “describe the reason for the payment difference”.
Tolerances come first: “The payment difference must be within both tolerances to be handled automatically” (the employee’s and the customer’s group), and it then posts “as either cash discount adjustment or unauthorized deduction”. Beyond the limit, “you must manually process it”.
In Dynamics 365 F&O, differences up to the Maximum penny difference post to the penny difference account; above it, with no cash discount, “the remaining amount is retained as an open balance on the payment transaction” (Microsoft Learn, 2026). Odoo keeps a partly paid invoice open with a Partial banner, or marks it paid and posts the difference to a chosen account (Odoo, 18.0). Oracle lets you write off underpayments (Oracle, Release 12.1).
Illustrative example (fictional figures). An invoice of USD 10,000 receives USD 9,500. As a partial payment, the USD 10,000 invoice and the USD 9,500 payment both stay open until the customer pays the rest. As a residual item, invoice and payment clear, and one new open item of USD 500 carries the reason code.
Our rule of thumb, not a standard: book a residual item when someone must investigate the difference (a deduction, a disputed price); book a partial payment when the customer has said it will pay the rest. The investigation: automating partial payments and deductions.
Which exceptions stop a posting, and what should the sender do?
Eight exceptions stop or change a posting: partial payments, short pays, small differences, overpayments, currency differences, closed periods, blocked accounts, and items that changed or were sent twice.
Exception table: what the ERP does and what the sending system should do
Behaviour depends on configuration and release; confirm it with your ERP team. For the unknown payer, see how to match a payment with no reference.
Write one rule per row before go-live and have the controller sign it off. A sending system that follows the ERP’s tolerances never sends a difference the ERP would refuse.
Currency. SAP posts realized exchange rate differences automatically “to the revenue or expense account as realized gains or losses” (SAP Learning, S/4HANA course). Oracle “records a realized gain or loss amount” for foreign-currency receipt applications (Oracle, Release 12.1); Business Central uses its Realized Gains and Losses accounts (Microsoft Learn, 2025). Missing accounts make the posting fail: test them in the pilot.
Blocks. In Business Central, a customer blocked with All means “No transaction is allowed for this customer, including payments” (Microsoft Learn, 2025). In SAP, a customer can be blocked for posting per company code. The sender routes the block to its owner and never removes it.
Stale items. Between match and posting, a colleague may clear the invoice or post a credit memo. Re-read each item immediately before posting.
What happens to payments that arrive in a locked or closed period?
In a locked or closed period the ERP refuses the posting or moves its date, so check the period first and follow an agreed rule: hold it, or post on the next open date.
- SAP: posting periods “can be handled differently for different account types”, so customer postings may be open while vendor postings are restricted; several company codes can share one posting period variant (SAP Learning, S/4HANA course).
- NetSuite: after Lock A/R, only users with Override Period Restrictions can post, and “No one can make general ledger impacting changes to posting transactions in a closed period” (Oracle NetSuite, help center).
- Dynamics 365 F&O: each legal entity’s ledger calendar sets the period status and “which users can post accounting transactions to periods” (Microsoft Learn, 2026).
- Odoo: a lock date “prevents posting new entries with an accounting date on or before the lock date”; the system then sets the accounting date to the day after the lock date, and the Hard Lock date “cannot be changed or overridden, regardless of access rights” (Odoo, 18.0 documentation).
Our guidance for month-end (illustrative rule). Agree a cut-off with the controller: payments from the month’s last bank statement post with that month’s date until the AR period locks; later ones post on the first open date, with a person’s approval. Keep the value date, and never let a sending system ask to reopen a period.
How do you correct a wrong clearing or posting?
Correct a wrong clearing by reversing it in the ERP, which reopens the items, then posting the right clearing; the ERP’s reversal document is the ERP’s own record.
In Business Central, unapplying creates correcting entries that “are the same as the originals but have an opposite sign in the Amount field”, and “the entries that the application closed are reopened”; the latest application is unapplied first (Microsoft Learn, 2025). SAP resets a clearing; Oracle unapplies a receipt and applies it again.
A correction is a posting too: Transformance can initiate and post a reversal back to the ERP after a person approves it, and the audit log stores the same fields as for any other action. Detail: what an AI agent’s audit trail records.
How does Transformance post payments and clear open items in your ERP?
Transformance posts, clears and writes journal entries back, with the method chosen for your requirements, and nothing posts without a person’s sign-off after 100% posting validation.
ClearMatch reaches a 95% auto-match rate and runs end to end in under 8 minutes (Transformance customer data, 2026). For the rest, Vero, the Transformance agent, investigates the exception from Customer 360, fetches internal and external information to find more matches and proposes with the evidence. A person approves.
- Control: ERP postings sit inside the 4-level approval model (read, recommend, execute, post), with a human in the loop; thresholds by amount, entity and customer decide who signs off (who approves what).
- Audit: the log records the timestamp, what the system did, what the user did, who approved, the input and the confidence. Reversals are written back too.
- Connection: the ERP connection typically takes 2-3 days, and your IT team may be involved; the full rollout takes 4-8 weeks. In SAP: no custom ABAP, no modifications.
- Scope: several SAP company codes, NetSuite subsidiaries and Dynamics 365 legal entities in one environment; data hosted in your region, VPC, SSO/SAML and RBAC (how AI agents access ERP data safely).
The exception table is the list to settle with your controller before the first posting, whichever system sends it. All connections: which ERP systems Transformance integrates with.
Who Transformance is for
- ERP: teams that post and clear customer payments in SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations or Business Central, or Odoo, all running in production with customers; Oracle and Infor are supported.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centres.
- Payment volume: from under 1,000 to over 100,000 payments a month.
- Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
- Scope: cash application alone, or the full order-to-cash: cash application, deductions, AR collections and cash forecasting.
Conclusion: write the exception rules before the first posting
An external system clears open items reliably when every instruction carries the items, amounts and difference treatment, mirrors the ERP’s checks, and sends every exception to a person first. Start with one entity and a signed-off exception table; widen once the pilot shows no stale or duplicate postings.
Key terms
- On-account cash: a payment posted to the customer account without clearing an invoice.
- Short pay: a payment below the invoiced amount; the difference becomes a residual item or deduction.
- Journal entry: the ledger posting that a clearing or a difference creates.
- Period close: locking a period so that no further postings land in it.
- Write-off: posting a small or uncollectable difference to an expense account.
- Foreign exchange rate: the rate that turns a currency difference into a realized gain or loss.
Related guides
- Which ERP systems does Transformance integrate with?
- What data does AR automation read from and write to the ERP?
- Who approves what when an AI agent works in your ERP?
- What does an AI agent’s audit trail in finance record?
- How does Transformance integrate with SAP S/4HANA?
- How do AI agents work with SAP for accounts receivable?
Frequently Asked Questions
Can an external system clear open items in SAP?
Yes: an external system can send SAP S/4HANA or ECC a payment with the open items it clears, and SAP creates the clearing document and runs its own period, account and tolerance checks at posting.
What is the difference between a partial payment and a residual item?
With a partial payment the invoice and the payment both stay open; with a residual item the invoice and payment are cleared and one new open item carries the difference, usually with a reason code.
What happens if a payment arrives after the period is closed?
The ERP refuses a posting dated in a closed period, so the payment is held or posted on the first open date under a rule your controller agreed, with the bank value date left unchanged.
Which ERPs can Transformance post payments to and clear open items in?
Transformance posts, clears and writes journal entries back in SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite, Dynamics 365 Finance & Operations, Business Central and Odoo, all in production with customers, with the method chosen for your requirements; Oracle and Infor are supported.
How long does it take to connect Transformance to the ERP for posting?
The ERP connection typically takes 2-3 days, and your IT team may be involved; the full rollout takes 4-8 weeks, and a proof of value runs in 4-5 weeks on one entity.
Does it work for groups with many entities and high payment volumes?
Yes: Transformance is built for 250 to 2,000+ employees and from under 1,000 to over 100,000 payments a month, with several SAP company codes, NetSuite subsidiaries or Dynamics 365 legal entities in one environment.
What does it cost to automate payment posting and clearing?
The cost depends on scope (cash application alone or the full order-to-cash) and on the number of entities, so we size it with you on a call: Book a Call.
SAP, SAP S/4HANA, Microsoft, Dynamics 365, Business Central, Oracle, NetSuite, Odoo and Infor are trademarks of their respective owners (SAP SE, Microsoft Corporation, Oracle Corporation, Odoo S.A., Infor). Transformance is not affiliated with or endorsed by them.
