Five Payment Channels Reconciled and Booked to AJUR Every Month

We delivered a monthly reconciliation and booking system that runs unattended on self-hosted n8n. Matching and the accounting import are not two projects. They are one automation.

Seven inputs, one format

We read two bank statements, two Stripe exports, PayPal, Wise and the CoinGate ledger, and convert each into one internal format regardless of the encoding or layout the provider uses. Every order starts from the master order register, and the order's payment method picks the matching route.

A matching engine for each payment route

Tracing every hop

• Each pass through an intermediary account is followed and booked. The trail runs from the order through the processor and the intermediary account to the bank line and the final accounting entry.
• Crypto price gaps between invoice and sale post automatically to exchange gains or losses.
• VAT per customer. We check each invoice for where the customer is based and whether it is a business or a private person, then apply domestic, EU or non-EU treatment.
• Multiple currencies. Each transaction gets currency conversion and a supplier-to-account mapping.

Sorting outgoing payments

Outgoing bank lines pass through rules in a fixed order, and the first rule that fits wins. The first rules pick out bank fees, internal transfers, salaries, tax authority payments and related-party movements. The rest go to a supplier account based on the country of the counterparty's bank: domestic, EU, non-EU, a cash withdrawal or a bank charge. Card payments have no counterparty IBAN, so we take the country from the merchant description. A line that gets through every rule unmatched goes on a checking list. Nothing receives a default without someone seeing it.

A file the old system will accept

AJUR takes one thing only, its own file. That file uses a custom delimited format, a set encoding, a block structure and sequential registration numbers. We turn each reconciled transaction into a debit and credit entry in precisely that format. The automation builds and delivers the file. The accountant runs the import and decides what gets posted and when.

• Re-runs are safe. Running again rebuilds the whole month as a new batch, not a delta that might clash with numbers already imported. Older batches stay on record.
• Reporting. Each month a report lists every transaction with its status, its match and its accounting entry. Flagged rows sit apart in a review queue.

Stack