Stripe
Payment acceptance and subscription billing, and for many companies the origin of all revenue data.
What it does
Stripe handles card and bank payments, subscriptions and invoicing. For most companies that sell online, it is where revenue begins.
Why it matters next to an AI-native ERP
The design question is not whether the ERP can connect to Stripe. It is how much detail should land in the ledger. Posting every transaction gives you granularity and a very large general ledger. Posting a daily summary keeps the ledger clean and pushes the detail into reporting. The right answer depends on volume and on what your auditors expect to see.
Fees, refunds, chargebacks and payout timing are where reconciliations usually break, because the payout that reaches your bank is a net figure covering many transactions across a date boundary.
How we implement it
We agree the summarisation level first, then map fees, refunds, chargebacks and payouts to accounts, and build the reconciliation between the Stripe balance and the bank. Where the ERP handles Stripe natively we use that. Where it does not, we treat the integration as a design decision rather than a switch to flip.
We implement this alongside Campfire, Rillet and DualEntry. If you are working out how it should connect to your ledger, that is the conversation we have every week.