Payments, collections and reconciliation

Flag transactions that don’t match across records

Done by about 9 million people across 8 job roles, several times a day.

When matching transaction records arrive from two sources → then Flag the mismatched transaction for review

Acts when the amount variance is more than 0. Otherwise it logs that the amounts from both sources match, and stops.

Reads

transaction id, source a amount, source b amount, source a name, source b name, transaction date

Evidence

Proved in test: n8n execution 1177, 12 of 20 nodes ran in 432 ms.

Process and record customer bill payments

Done by about 14.1 million people across 12 job roles, several times a day.

When a customer submits payment for a bill → then Record customer bill payment

Acts every time the trigger fires.

Reads

payment id, customer name, bill amount, payment amount, payment date

Evidence

Proved in test: n8n execution 1330, 9 of 11 nodes ran in 315 ms.

Flag register mismatches at shift close

Done by about 6 million people across 5 job roles, several times a day.

When shift or register closing report submitted → then Flag register mismatch for review

Acts when the variance is more than 0. Otherwise it logs that the recorded and expected totals match, and stops.

Reads

shift id, employee name, recorded total, expected total

Evidence

Proved in test: n8n execution 1162, 12 of 20 nodes ran in 451 ms.

Log sale and transaction details automatically

Done by about 3.8 million people across 6 job roles, several times a day.

When a sale or transaction is completed → then Log transaction to sales record

Acts every time the trigger fires.

Reads

transaction id, transaction amount, transaction date, payment method, cashier id

Evidence

Proved in test: n8n execution 1281, 9 of 11 nodes ran in 336 ms.

Charge customers the fare when they board

Done by about 4.3 million people across 10 job roles, several times a day.

When a customer boards or requests the service → then Record the fare charge for the trip

Acts when the fare amount is more than 0. Otherwise it logs that the fare is zero, nothing to charge, and stops.

Reads

trip id, customer id, fare amount, boarding time, payment method

Evidence

Proved in test: n8n execution 1048, 10 of 13 nodes ran in 410 ms.

Mark accounts current or delinquent automatically

2 builds of this one. The same workflow, fitted to what each business calls it and the field it checks — listed in the teardown below.

Done by about 1.7 million people across 4 job roles, several times a day.

On a schedule Every day, check accounts against their payment due date → then Mark account delinquent

Acts when the amount shortfall is more than 0. Otherwise it logs that the full payment was received, and stops.

Reads

account id, due date, payment amount, amount received

Evidence

Proved in test: n8n execution 1304, 12 of 20 nodes ran in 712 ms.

Send confirmation after advance payment received

Done by about 43,000 people across 1 job role, daily.

When an advance payment is received for a registration → then Send registration confirmation

Acts when the deposit shortfall is at least 0. Otherwise it logs that the payment does not yet cover the required deposit, and stops.

Reads

registration id, customer email, payment amount, required deposit, payment date

Evidence

Proved in test: n8n execution 1396, 12 of 20 nodes ran in 464 ms.

Record payment when permit fee is due

Done by about 180,000 people across 1 job role, several times a day.

When a permit or license is issued with a fee due → then Notify clerk to collect permit fee

Acts when the balance due is more than 0. Otherwise it logs that the fee was already paid at issuance, and stops.

Reads

permit id, permit type, fee amount, amount paid, issue date

Evidence

Proved in test: n8n execution 1354, 12 of 20 nodes ran in 547 ms.

Send overdue or lost item notices

Done by about 69,000 people across 1 job role, daily.

On a schedule Daily check for items overdue or lost → then Send overdue item notice

Acts when the days overdue is at least 1. Otherwise it logs that the item is not yet overdue, and stops.

Reads

loan id, customer name, customer email, due date, item name

Evidence

Proved in test: n8n execution 1406, 12 of 20 nodes ran in 452 ms.