{"id":159,"date":"2026-11-07T09:00:00","date_gmt":"2026-11-07T08:00:00","guid":{"rendered":"https:\/\/yindle.com\/?p=159"},"modified":"2026-09-21T22:09:31","modified_gmt":"2026-09-21T20:09:31","slug":"lifecycle-netto-webshop-afas-reconciliatie","status":"publish","type":"post","link":"https:\/\/yindle.com\/en\/finding-revenue-discrepancies-with-lifecycle-net-per-order\/","title":{"rendered":"Finding revenue discrepancies with lifecycle net per order"},"content":{"rendered":"

Find revenue discrepancies by comparing the full financial lifecycle of each order: payments and captures minus refunds and chargebacks, against AFAS invoices and credit notes. Comparing gross daily totals can let two opposing errors cancel out and does not identify which order is still missing a financial document.<\/p>\n

Why separate totals provide false reassurance<\/h2>\n

Suppose one refund is missing and another order is posted twice for the same amount. The daily total may reconcile exactly while both customer records are wrong. Payment, settlement, invoice and credit may also occur on different days or even in different months. Reconciliation therefore needs to follow order identity and lifecycle, with an explicit as-of date for each source.<\/p>\n

Calculate a technically expected net amount for every order from the supported payment events. Compare it with the sum of linked AFAS documents under the model approved by the accounting team. Keep \u201csource not refreshed yet\u201d, \u201cdocument still within the normal delay\u201d and \u201csubstantive discrepancy\u201d as separate outcomes.<\/p>\n

Reconciliation table per order<\/h2>\n
\n\n\n\n\n\n\n\n\n\n
Check<\/th>\nSources<\/th>\nExample signal<\/th>\n<\/tr>\n<\/thead>\n
Gross lifecycle<\/td>\nWooCommerce and payment provider<\/td>\nMissing or duplicate capture<\/td>\n<\/tr>\n
Adjustments<\/td>\nRefunds and chargebacks<\/td>\nRefund paid but not posted<\/td>\n<\/tr>\n
ERP documents<\/td>\nAFAS invoice and credit note<\/td>\nDocument missing beyond the agreed age<\/td>\n<\/tr>\n
Lifecycle net<\/td>\nAll linked events<\/td>\nNet discrepancy outside tolerance<\/td>\n<\/tr>\n
Provenance<\/td>\nIdentities and execution register<\/td>\nAmbiguous or manual match<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

Only use amounts after identities have been verified. A coincidentally equal total is not a match. Connect<\/a> can bring source events and AFAS results together in the same technical check.<\/p>\n

Fictional example: the net amount only reconciles after a late credit<\/h2>\n

Fictional example: order LN-502 from lighting shop Noorderlicht was paid for 240 euros. A portion of 40 euros is refunded. The expected lifecycle net is therefore 200 euros. The AFAS invoice for 240 euros is already available, but the credit note only appears the next morning. The first reconciliation shows \u201cwaiting for credit within the agreed window\u201d, rather than immediately declaring a definitive financial incident.<\/p>\n

After the next source refresh, the credit is linked and the order reconciles at 200 euros. LN-503 also has a refund of 40 euros, but a credit is still missing after the configured age, and the technical execution register shows no initiated credit posting. That order receives targeted attention. This example is fictional and does not determine which periods or postings are financially correct; it illustrates how lifecycle and age together reduce noise.<\/p>\n

Make discrepancy reasons actionable<\/h2>\n