← Noesa

Finance for Integrators

For Backend devs automating an online store's billing — invoices, payments, refunds, payouts — and the finance behind each. · 18 days · Tech

A 18-day course
One short lesson a day · go at your own pace
Log in to start
The days
Listen to the whole course · 84 min
  1. 1The money story: from a sale to the booksTrace what happens after a customer buys a license — which teams touch it and in what order — so you know exactly where your integration sits and who owns what comes next. Listen · 5 min
  2. 2Reading the ledger without building oneRead any accounting entry and say what moved where — enough to follow a finance conversation, without ever needing to post one yourself. Listen · 5 min
  3. 3Five account types and the one equationClassify any account into one of five types, and predict which direction — debit or credit — increases it. Listen · 5 min
  4. 4Accounts Receivable, from order to cashFollow an invoice from order to cash in both the prepaid and the invoiced flow, and name what Accounts Receivable owns at each step. Listen · 4 min
  5. 5Revenue recognition and deferred revenueExplain when a license sale becomes income, and why cash you collected isn't yet revenue you've earned. Listen · 5 min
  6. 6Invoices, credit notes, and adjustmentsSay why a correction is a credit note or a reversing entry, never an edit, and what that means for the data your store keeps. Listen · 5 min
  7. 7Accounts Payable: the other side of the moneyDescribe what Accounts Payable does and name the two store events — refunds and partner payouts — that flow through it, so you know which team owns money leaving Meadow. Listen · 5 min
  8. 8Tax I: sales tax, VAT, and GSTPut the right consumption tax on an invoice given the customer's country, the selling entity, and the product's classification — and name which of India GST, EU VAT, or US sales tax applies. Listen · 5 min
  9. 9Tax II: cross-border, withholding, and e-invoicingExplain the three things that change when a sale crosses a border — withholding tax, reverse charge, and e-invoicing/clearance mandates — and what each demands from your store data. Listen · 5 min
  10. 10Multiple legal entities and inter-companyExplain why one business runs several legal entities, and apply the rule that decides which Meadow entity should invoice a given customer. Listen · 5 min
  11. 11Multi-currency: one sale, two numbersHandle a sale made in the customer's currency and explain where exchange differences come from between invoicing and payment. Listen · 5 min
  12. 12Reconciliation: books vs bank vs gatewayExplain what bank and payment-gateway reconciliation prove, and why clean, idempotent store data is what makes both possible. Listen · 5 min
  13. 13Periods and closeExplain what an accounting period is, what "closing" and "locking" a month or year mean, and why the timestamp on your store's data decides which period a sale falls into. Listen · 5 min
  14. 14The report mapMap which report each finance team lives in, what's specific to one team, and what's shared — so you know who reads the store facts you emit, and where. Listen · 5 min
  15. 15Revenue reportingRead a revenue report and distinguish billed, recognized, and collected revenue, and read revenue split by product, entity, and country. Listen · 5 min
  16. 16Tax filing reportsName the main tax-filing reports per jurisdiction — India's GSTR-1/3B/2B, the EU VAT/OSS return, and TDS/withholding — and state what store data each is built from. Listen · 5 min
  17. 17Audit and complianceExplain what an audit verifies and name the non-negotiables your store integration must preserve so an independent stranger can trust the books. Listen · 5 min
  18. 18Capstone: one sale, end to endTrace a cross-border license sale through every team and every report end to end — for both the prepaid German customer and invoiced Ridgeline — and leave with the decision checklist that makes you autonomous. Listen · 5 min