How do you build a first cash flow statement your auditor can follow?
How do we prepare our first cash flow statement from the general ledger so it holds up in the audit? Current guides explain the indirect method, net income plus depreciation plus working capital changes, and stop there. The SEC Chief Accountant has called the statement a leading area of restatements and says a classification error is not immaterial by default. We built one example year for a software company two ways. A mechanical build that dropped each balance sheet change into a section ended on the right cash balance, 505,000 dollars of net change, and still overstated operating cash flow by 50,000, or 14 percent, and investing outflows by 80,000. The cause was three ordinary events: equipment still unpaid at year end, equipment financed by the vendor, and a term loan shown net. Here is the example, the three fixes, five checks to run before the auditor arrives, and how Rivane builds the statement today.
Recurring journals can run on their own and still pass review.
How do we set up recurring journal entries so they do not post twice, slip off month end, or land in a closed period? Current answers list the parts of a good setup, a template, a schedule, approval and evidence, and stop there. We took one example register of four templates, 38 entries and 330,300 dollars in a year, and worked through the three things that go wrong in practice. A rent template set to every 30 days posted nothing in February and twice in May. Stepping from the last date instead of the start date moved every entry after February to the 28th. A sublease signed after September closed put 6,800 dollars into months that were already locked. Here is the example, the schedule rules that avoid each problem, five tests to run on any system, and how Rivane runs recurring journals today.
Should departments live in the chart of accounts or in a dimension?
Should a growing company add more GL accounts or use dimensions like department and location? Current answers say dimensions and show the multiplication, but not how to decide a single split or how to move the history. We took one example QuickBooks chart with 211 active accounts, departments and offices built into the account names, and added two ordinary requests: a new Marketing department and payroll by office. The chart grew to 354, past the 250 account limit Intuit lists for QuickBooks Online Plus. Rebuilt as natural accounts with three dimensions it had 143, and the same requests added none. Here are the five questions that decide account or tag, the mapping and tie out that moves the history, and how Rivane holds accounts and dimensions today.
Build the expected column before you run the flux.
Should month end flux analysis compare against last month, the same month last year, or the budget? Current answers say to run all three and pair a percentage with a dollar threshold. We built one example March close for a software company, nine income statement lines with four errors planted in them, and ran every basis. With a common 10 percent and 25,000 dollar rule, the same month last year flagged none of the four errors, and last month and the budget flagged two each. Lowering the amount floor to 10,000 and judging new balances on amount alone caught all four on every basis. What changed between bases was the noise: seven lines to explain against last year, five against last month or the budget, and four against last month plus the changes the team already knew about. Here is the example, how to build that expected column, and how Rivane runs flux today.
A journal approval threshold needs a rule for the controller’s own entries.
Should every manual journal entry need approval, or only those above a threshold? Current answers give an example number, 50,000 or 100,000 dollars, without showing what it sends for approval or what it leaves out. We took one example month of forty manual entries from four people and counted. A 10,000 dollar threshold sent 14 entries for approval and covered 82.1 percent of the value. It also let five of the six estimates posted by the controller and the CFO through with no second person, and sent the sixth, a 140,000 dollar bonus true-up, to the controller who had posted it. Two rules on who posted the entry, placed ahead of the amount rule, raised the count to 19 approvals and put every estimate in front of someone else. The other 21 entries, 85,960 dollars in all, are covered by one signed review after posting. Here is the count, what Sage Intacct and NetSuite give you, and how Rivane routes journal approvals today.
Why do two companies in the same group disagree about what they owe each other?
Why don’t our intercompany balances match? Most current answers list the usual causes, timing, currency and missing entries, and stop there. We built one example September close for a three company group, a US parent, a German subsidiary that keeps its books in euros, and a second US company, and ran it through Rivane’s intercompany matching code. The parent and the German subsidiary disagreed by 120,991.81 dollars. Five items explained it: a shipment booked twelve days apart across the month end, a recharge booked 400 dollars short, an interest charge never booked, a consulting invoice booked against the wrong group company, and 4,141.81 dollars of exchange difference. Fixing the four journal breaks still left the balances 3,963.63 dollars apart, outside tolerance. That gap closes only when the subsidiary revalues its dollar payables at the closing rate, as IAS 21 requires, and the resulting loss stays in consolidated profit after the balances are eliminated. Here is the example, a close order that ends with matching balances, what Oracle and SAP give you, and how Rivane matches today.
Count the emails before you switch dunning on.
When we switch on automated dunning, what happens to invoices that are already overdue? Current guides give a cadence for a single late invoice: a reminder at 7 days past due, then 15, 30 and 45. They say nothing about the first run, when that ladder meets a backlog. We ran one example backlog of twelve overdue invoices across five customers through five rules, all using the same 7, 15, 30 and 45 day ladder. Sending every step an invoice has reached sent 23 emails on the first morning, eight of them to one customer, and the final demand to two customers who had never had a reminder. One letter per customer, starting everyone at the first step, sent five. Adding a pause for disputed invoices and a phone call for anything past the last step sent three emails and put two customers on a call list. Here is the test, what Dynamics 365, NetSuite and SAP do with a backlog, a go-live checklist, and how Rivane runs dunning today.
If two bank lines share an amount, let the reference decide.
What date range should we set for bank reconciliation auto-matching? Current answers give a number: three days in NetSuite’s built in rule, or five days for checks and two for ACH and wires in one recent guide. We ran eleven statement lines from an example month through six rules. Widening the window from one day to ten days did not add a single correct match. It turned clean matches into ties, because the same amounts recur: annual plan receipts, contractor payments, a check and an ACH for the same sum. A rule that takes the closest date on a tie matched seven lines and got two of them wrong, one of which hid a customer payment that never arrived. Matching on the reference first, then refusing to auto-match any tie, got ten lines right, none wrong, and left only the bank fee to post. Here is the test, what NetSuite, Oracle and Microsoft do with a tie, a starting rule set, and how Rivane matches today.
Two numbers decide which supplier invoices your team never sees.
What price and quantity tolerance should we set for invoice matching? The current answers agree there is no single right number, and the best of them say to test a few candidate settings against last quarter’s invoices before choosing. None of them shows what that test looks like. We ran it on seven example invoice lines carrying 3,790 dollars of overbilling. A 2 percent price tolerance on its own cut the review queue from six lines to two, and let 1,790 dollars through without anyone looking. Adding a 250 dollar ceiling per line, checked alongside the percentage, kept four lines in review and let 50 dollars through. A small unit price floor, the third common design, waved through a 12.5 percent price rise on fasteners because it was one cent a unit. Here is how SAP, Oracle and Microsoft combine the two numbers, what an empty tolerance field means in each, a starting setting you can defend, and how Rivane applies its tolerance set today.
How should we measure the 20 percent we did not buy?
When a group buys 80 percent of a company under IFRS, paragraph 19 of IFRS 3 lets it measure the other 20 percent at fair value or at its proportionate share of the identifiable net assets, and the choice is made for each acquisition. Most answers stop at day one: fair value gives more goodwill. We followed one example acquisition for two years. On day one the two methods are 400,000 dollars apart in goodwill. When the subsidiary is later impaired, the proportionate method books the smaller total loss but puts a larger loss on the parent, and its grossed up test fails first. When the group buys the remaining 20 percent, the proportionate method takes 800,000 dollars out of parent equity against 400,000 under fair value. Here is what IFRS 3, IFRS 10 and IAS 36 say, read from the text, the worked numbers, a way to decide deal by deal, and what Rivane records for each subsidiary.
The setup fee that can outlast its first contract.
How do you recognize revenue on a SaaS implementation fee under ASC 606? Many current answers say implementation is typically a separate performance obligation, recognized when the work is done. The standard starts from the other end. ASC 606-10-25-17 says setup activities that do not transfer a service to the customer are not a performance obligation, and 606-10-55-51 treats the fee as an advance payment for the subscription, recognized over a period that runs past the first term when the renewal option is a material right. We ran one example contract four ways: a 60,000 dollar annual subscription with a 15,000 dollar implementation fee, starting 1 April 2026, with a 31 December year end. Depending on two judgements, 2026 revenue lands anywhere from 48,750 to 60,937.50 dollars, a 25 percent spread on the same contract. Here is what the Codification says, read from the text, how to test the renewal, the worked numbers, and how the same contract is set up in Rivane.
If a twelve month subscription starts on the 15th, count the days.
How do you amortize an annual software subscription that starts in the middle of a month? Current guides say to prorate the first month by days, and one sample schedule still runs a twelve month contract across twelve monthly periods. A contract that starts on 15 March runs to 14 March, so it touches thirteen calendar months, and the method you pick for the two part months decides the prepaid balance at year end. We ran one example through four common methods: a 36,000 dollar contract paid on 15 March 2026 with a 31 December year end. Counting days leaves 7,200.04 dollars of prepaid at year end. A half month in the first and last month leaves 7,500. Starting the following month leaves 9,000, which is 25 percent too much. Splitting the money equally over every month the term touches leaves 8,307.70 and charges the 17 days of March as if they were a full month. Here is how to pick a method, what IAS 1 says about the long term part of a multi year prepayment, why the tax schedule is a different schedule, and how to set up a day based schedule in Rivane.
Payday lands in January, and December still owes the wages.
How do you accrue payroll at year end when the pay date falls in January? Most answers give the same formula: daily payroll cost times the unpaid days, plus an allowance for employer taxes. The step they skip is which tax rate to use. IRS Publication 15 ties employment tax to the date wages are paid, so wages earned in December and paid on 8 January carry January rates, with the Social Security and FUTA wage bases reset to zero. One current guide advises the opposite, a smaller late year rate, which is right for a November accrual and wrong for this one. We ran an example: a 40 person team, a 200,000 dollar biweekly payroll, 180,000 of it earned in December. Priced at the load from the last December run, the employer tax accrual is 10,422 dollars. Priced at the January rates that will actually apply, it is 14,828. That is 30 percent short, every year, in the one month an auditor tests. Here is what Publication 15 and IAS 19 say, read from the documents, the worked numbers, and how the entries look in Rivane.
Choose a depreciation convention that holds up in a heavy fourth quarter.
Which depreciation convention should the books use: full month, mid month, mid quarter or half year? Most answers define the four and stop, and the half year rule people remember comes from the tax code. We ran one example year through all of them: a software company buys 240,000 dollars of laptops, servers and network kit on a three year life, with 62.5 percent of it arriving in November. Measured against the days each asset was actually in service, mid month lands within 217 dollars. Full month and next month miss by 3,550 and 3,116 dollars in opposite directions. Half year books 40,000 dollars against 25,616, which is 56 percent more depreciation than time in service supports, and it gets the February laptops wrong in the other direction. The tax code agrees that a heavy fourth quarter is the problem case: more than 40 percent of a year’s basis in the last three months switches MACRS to mid quarter. Here is what IAS 16, IAS 8 and IRS Publication 946 say, read from the text, the worked numbers, and the in service date that matters more than any convention.
Which of the ten balance types is your cash position reading?
Somebody compares the cash figure in the ledger with the figure on the bank portal and the two disagree. Every answer you can find explains the same list: outstanding cheques, deposits in transit, fees the bank booked first, keying errors. All of it is real, and all of it skips a question that comes first. Which balance are you comparing against? We downloaded the ISO 20022 external code sets, 2Q2026 publication, and parsed the package rather than reading a summary of it. ExternalBalanceType1Code carries exactly ten codes and ExternalBalanceSubType1Code carries twenty two more that qualify them, so one account on one day can be reported several times over with every figure correct. Three of the ten do the work. The closing booked balance is defined as the opening booked balance plus every entry booked in the period, which makes it the only balance you can recompute and therefore the only one a reconciliation can prove. The closing available balance is money at the account owner’s disposal, which is what you can actually pay from, and it is what a portal usually leads with. The expected balance projects the end of day if everything pending books and nothing else arrives, which is a same day forecast from the party with the best view of the inputs. They are stamped differently too: reading Bank of America’s own camt.053 reference guide in the file, the booked balance examples carry a plain date while the available balance example carries a time to the second. Then there is a trap that only appeared after the move off MT940. The sub type INTM marks a balance carried from one page of a multi page statement to the next, and the guide states the rule plainly: on page one an opening booked balance comes without INTM, and on any later page it comes with it. So a four page statement holds four balances of the same type and one of them is the real one. A reader that matches on type and ignores the qualifier takes a page marker for a period balance, and the qualifier has no MT940 equivalent, so a parser carried over from the older format has nowhere to put it. The code set also gives away two controls, because it states that an opening booked balance always equals the closing book balance of the previous report. Here is what the code set and the bank specifications say, read from the files, and the balance type, entry status and as of time that let a cash position say which number it is and when it was true.
Fifteen months is enough time to sort the tariff codes that split.
The eighth edition of the Harmonized System enters into force on 1 January 2028, and the World Customs Organization has already published both the amendments and the mapping from the codes you hold today. Its amendment page states 299 sets of amendments, a nomenclature of 1,229 headings and 5,852 subheadings, six new headings and 428 new subheadings created, and five headings and 172 subheadings deleted. Most coverage stops at that scope and advises starting early. The question a finance team needs answered is narrower: how much of the remap can a system do by itself. So we downloaded both WCO correlation tables and read Table II, which runs from 2022 to 2028, in the document rather than through a summary, then counted its rows. It lists 321 HS 2022 subheadings. Of those, 125 correspond to exactly one HS 2028 subheading, which is a straight substitution. The other 196 divide into more than one, 61 percent of the affected codes, and a division is a decision about each product rather than a lookup. In total the table carries 672 correlation pairs onto 548 distinct new subheadings, so neither direction is a function. Reading the divisions one by one is where it gets practical, because the attribute that picks the new code is almost never a finance attribute: 4407.29 divides across seven timber species, 3915.90 across twelve polymer and contamination categories, 0306.33 across eight crab species and states, and 3002.41, vaccines for human medicine, fans out across 38 subheadings of the new heading 30.07, disease by disease. Two more, 2107.10 and 2107.90, are listed against chapters with no source code at all, and the table declines to say which goods transfer. Then the systems half. A code master with an active flag can retire a deleted subheading, but a flag is not a date, and the same six digits mean different goods either side of the effective date while open orders, in transit stock and credit notes still reference the old meaning. Here is what the WCO tables say, read from the page, and the validity dates, product attributes and rate links that turn the next edition into a query.
If you reopen a closed month, the ledger should still know it was closed.
September closed on the fourth working day. In the middle of the October close somebody finds that a batch of September invoices was cut off a day late. Every ERP has a Reopen button and almost every help page explains how to press it. Sage, Oracle, Dynamics GP and Zuora all document the mechanics well. None of them answers when you should, and the accounting standard does, by keying off something your period lock cannot see. Read IAS 8 in the text and the hinge is whether the financial statements covering that period were authorised for issue. Paragraph 41 draws the line in one sentence, paragraph 5 defines a prior period error around the same moment, paragraph 42 corrects a material one retrospectively in the first statements authorised for issue after discovery, and paragraph 46 keeps that correction out of the profit or loss of the year you found it in. Whether the figure has to move at all is a materiality question, and SEC Staff Accounting Bulletin 108 asks for the same error quantified two different ways. We ran one cut-off case through both. An error of 212,400 dollars sitting at the current year end, with 347,900 dollars of the same error in the prior year, is 135,500 dollars under the rollover approach and 212,400 dollars under the iron curtain approach, which is 3.23 percent and 5.06 percent of a 4.2 million dollar pre-tax income. A five percent rule of thumb answers the identical question in opposite directions, which is one reason SAB 99 says exclusive reliance on a percentage threshold has no basis in the accounting literature or the law. Correct either side on its own and what remains grows to 347,900 dollars, 8.28 percent, larger than either number that started the conversation, because the prior year is where the error actually lives. Then there is the systems half, which nobody writes about: a reopen clears the closed timestamp, after which the period is indistinguishable from one that was never closed, and the backdated entry looks like ordinary current work. Here is what the standards say, read from the text, and the durable reopen marker, dual control, derived prior period flag and sealed terminal state that let a reopened month still prove when it was closed.
One payment, twelve invoices, and the list that has to travel with it.
A customer sends one ACH credit for 340,812 dollars. It covers twelve open invoices, it matches none of them, and the remittance advice is in somebody’s inbox. The Federal Reserve Bank of Cleveland published a research brief on 25 September 2026 that names this exact case: a single payment aggregated to cover multiple underlying remittance items, which needs an AR system capable of complex parsing logic to fully automate. We measured what happens when it does not have one. Running an example book of 960 open invoices and 666 receipts through the reconciliation engine published on this site, 42 lump-sum receipts are 6.3 percent of the receipt count and 34.9 percent of the cash. At the default settings the engine matches 93.7 percent of receipts and 65.1 percent of the money, leaving 336 invoices open, and every one of its 624 matches is correct. Widen the date window from three days to a year and the amount tolerance from zero to 1,000 dollars and the numbers do not move at all, because the engine consumes each row once and no single invoice equals a lump sum. Push the amount tolerance to 100,000 dollars and the match rate climbs to 99.2 percent of receipts and 94.3 percent of value while only 310 of 661 matches stay correct, with 7,583,620.03 dollars landing on the wrong invoice. Solving for the combination instead has its own limit: across 20,000 trials on a book with six repeated price points, more than one subset of a customer’s open invoices summed to exactly the amount received in 100 percent of cases, 2,794 of them on average. Invoice to the cent with no repeated amounts and that falls to 8.85 percent. Here is what the Fed brief actually says, read from the page, and the remittance, allocation and evidence work that turns a lump sum into twelve postings you can show.
How much of your first audited year is already sitting in deferred revenue?
A software company heading into its first audit usually prepares the deferred revenue rollforward for the year under audit. The balance that decides whether the revenue number holds is the one on the opening row, set before any auditor looked at the books. AU-C 510 and ISA 510 require the auditor to obtain sufficient appropriate evidence that opening balances do not contain misstatements that materially affect the current period, and to qualify or disclaim the opinion if they cannot. Receivables partly prove themselves by being collected. Deferred revenue clears by becoming revenue, which is the number under audit. We ran an example book through the revenue recognition calculator on this site to size it. Twelve customers at 120,000 dollars a year, invoiced annually in advance and spread across 2025, leave 660,000 dollars deferred on 1 January 2026: 45.8 percent of 2026 revenue if the book is flat and 29.7 percent if it doubles. Billed three years upfront, every dollar of 2026 revenue comes from the opening balance. If last year’s invoices went straight to revenue, the audited year is off by the unearned portion in one direction or the other. ASC 606-10-50-8(b) and IFRS 15.116(b) turn the released amount into a disclosure, and 606-10-50-11 lets a private company leave it out while still disclosing opening and closing balances. Here is how to size your own figure and the contract level schedule that turns the opening balance into a recomputation.
A journal entry becomes audit evidence the moment somebody keys it.
ISA 240 (Revised) is effective for audits of financial statements for periods beginning on or after 15 December 2026, which for a calendar year company is the year starting in January. So the entries the standard reaches are the ones about to be posted, not ones already filed. The coverage so far has been about the auditor: a fraud lens, a stand back requirement, more documentation. Read the approved pronouncement and one requirement lands squarely on the company instead. Paragraph 49(b) asks the auditor to obtain audit evidence about the completeness of the population of journal entries and other adjustments made throughout the period, not a sample from the last week of December, and paragraph 47 says that work happens irrespective of how the risk of management override was assessed. Paragraph 68(b) then makes the auditor document how their understanding of your posting process was obtained and from which sources, which pushes the answer toward a system report rather than a walkthrough. Appendix 4 names the characteristics an inappropriate entry tends to carry, and read as a column list they are specific: entries to seldom used accounts, entries by people who do not normally post, entries at period end with little or no description, adjustments made while the statements are being prepared that carry no account number, and round or repeating amounts. Only one of those five is a figure. The other four are metadata, which is the part a system treats as optional and the part that cannot be reconstructed once the year closes. There is also a comfortable assumption worth testing first. Running 100,000 trials against the published logic of the trial balance checker on this site, a balanced reclassification between two accounts was reported as in balance 100,000 times out of 100,000 with no row flagged for review, while a one sided corruption of the same size was caught every time. A ledger that ties is complete evidence about arithmetic and silent on appropriateness. Here is what the approved text says, read from the pronouncement, and the preparer, timestamp, description, classification and numbering work that turns the population request into a query.
Get four fields ready before California taxes your software in 2027.
California signed SB 122 on 29 June 2026 and Colorado signed HB 26-1223 on 4 June 2026. From 1 January 2027 both states tax prewritten software however it is delivered, which includes a subscription your customer reaches through a browser. The headline is everywhere. What is less covered is that the statute does not key off your product, it keys off four fields on records you already keep, and most billing systems leave three of them blank. Read the chaptered bill rather than a summary and they are easy to name. Section 6010.5(b)(3) sources a remote sale to the purchaser’s known address in California, taken from your records in a fixed order of priority: billing address, then shipping, then the address on the payment instrument, then the mailing address. With no California address on file the sale is deemed to be outside the state, and section 7202.1 sends the district rate down the same path, so one address field carries the local money too. Sections 6052 and 6201.55 add a threshold nobody has had to track before: once a single customer passes five million dollars of digital product purchases in a calendar year, the obligation to remit moves to that customer, who issues you a certificate against a direct payment permit that section 7051.3(d) issues for twelve months at a time. Section 6010.9 keeps the custom software exemption alive for modification work, but only where the charge is separately stated on the invoice. The CDTFA draft package published on 1 September 2026, with comments closed on 24 September, treats each subscription period as a continuing sale, so periods before 1 January 2027 stay untaxed and the service period on the line decides the answer rather than the invoice date. Running the calculator published on this site, a 240,000 dollar annual subscription to a San Francisco address carries 20,700 dollars of tax, and absorbing it instead of passing it on costs 19,056.39 dollars of revenue. Here is what the two statutes say, read from the text, and the address, catalogue, threshold and service period work that turns a tax change into a billing change.
Company cars and medical cover become monthly payroll numbers in 2027.
From 6 April 2027 a UK employer can no longer report company cars, car fuel, vans, van fuel or employer provided medical benefits after the end of the tax year. HMRC confirmed the phasing in June 2026: those five benefits move into real time payroll reporting first, most of the rest follow in April 2028, and loans and accommodation stay voluntary. The dates are widely covered. What gets less attention is the arithmetic underneath, and that is where the work actually lands. Today a benefit value has to be right once a year, with a tail that runs to 6 July for the P11D and 22 July for the Class 1A payment. From April 2027 it has to be right before every payroll cut off, and the data still sits with the fleet provider and the medical insurer rather than in payroll. Read the interim guidance directly and the useful surprise is what HMRC asks for. It does not ask for accuracy, it asks for timeliness: report when you become aware of a benefit or can estimate its value, report as close to the relevant pay period as possible, do not wait for the end of the year, and no penalty applies where a reasonable estimate was used because the information was not there. From 2028 to 2029 the penalty list names the opposite behaviour, reporting everything at the end of the year, as a thing that gets penalised. There is a second piece of arithmetic worth knowing before you set a tolerance. HMRC says to divide the cash equivalent by the number of pay periods and round down to two decimal places, so the payroll total is structurally below the benefits register, every time. We measured it across all two million cash equivalents from one penny to twenty thousand pounds: on a monthly payroll only 8.3333 percent divide to the penny, the average shortfall is 5.5 pence a line a year and the ceiling is 11 pence. Running a 250 line register through the reconciliation tool published on this site, a zero tolerance match closed 20 of 250 lines and a 12 pence tolerance closed all 250. Here is what the guidance says, read from the text, and the monthly benefit cut off, estimate policy, reconciliation tolerance and evidence trail that turn an annual form into a payroll input you can actually run.
When a supplier sends new bank details, the first check is yours to make.
A supplier emails new bank details, someone updates the vendor record, and the next payment run sends the money. Since 9 October 2025 every euro area payment service provider has had to offer Verification of Payee, so it is tempting to assume the bank now catches this. Read Article 5c of Regulation (EU) 2024/886 and two things become clear. The check is tied to a payment, so it cannot run at the moment you change the record: the European Payments Council answers the vendor onboarding question directly and says verification happens when the first payment is initiated and for each one after that. And Article 5c(6) lets a payer that is not a consumer opt out when it submits payment orders as a package, which is exactly what an ERP payment run does. Deutsche Bank measured the result on its own EBICS channel: around 84 percent of corporate SEPA credit transfer files were opted out in October 2025, still about 80 percent by January 2026. Article 5c(8) leaves the payer carrying the loss once the provider has done its part, and the EPC states plainly that there is no liability shift toward the bank. The good news is that the control this leaves you owning is small and ordinary. We ran the IBAN checker published on this site over a million random corruptions per case: every single digit typo was caught, while two digit corruptions still validated about 0.7 percent of the time, roughly one in 145, and a correctly formed IBAN belonging to somebody else passes every format test there is. Here is what the Regulation actually says, read from the text, the two bulk patterns the European Commission has confirmed work, and the versioned supplier bank record, identifier based matching and exception query that make the change itself the control point.
A repair now adds a year to the guarantee, and your provision can see it coming.
From 31 July 2026 the rules promoting the repair of goods apply across the European Union, and the after-sales phase most finance systems treat as an afterthought gets a shape you can measure. Directive (EU) 2024/1799 does two things a finance team should care about. It amends the sale of goods rules so that when a consumer chooses repair to bring a good back into conformity, the legal guarantee period is extended once by 12 months, added to the time that was left. And it puts an obligation on the manufacturer to repair, on request, goods for which repairability requirements already exist in Union law, at a reasonable price and within a reasonable time, with spare parts offered at a reasonable price that does not deter repair and indicative repair prices published on a free website. Read the transitional rule closely, because a fetched summary gets it wrong: the guarantee extension applies only to sales contracts concluded on or after 31 July 2026, while the obligation to repair reaches goods already placed on the market. The work this asks for on your side pays for itself. A guarantee end date stops being a static field set at the sale and becomes a per unit date that a repair event can move. A spare part becomes an item with an availability window measured in years and a reasonable price rule the pricing engine can evidence. A repair quote becomes a priced offer that holds for 30 days and binds once accepted. Here is what the Directive says, read from the text, and the guarantee clock, service parts catalogue and repair record that turn an obligation into an after-sales line you can plan, provision and prove.
Do you know what each piece of your finance stack can reach?
Since 11 September 2026, Article 14 of the EU Cyber Resilience Act has required the manufacturer of a product with digital elements to report an actively exploited vulnerability to a national CSIRT and to ENISA within 24 hours, with a fuller notification at 72 hours carrying the mitigations users can apply, and a final report within 14 days of a fix being available. ENISA’s Single Reporting Platform went live the same day. The part that reaches buyers sits in Article 14(8): the manufacturer must also inform the impacted users, where appropriate in a structured, machine-readable format that is easily automatically processable, and where it fails to do so in time the notified CSIRTs may inform users themselves. The Commission confirms the duty covers products already on the market, so the tax engine installed in 2019 and the bank connectivity agent nobody has upgraded are both inside it. That is a faster and better signal about your own software than finance teams have had before. Whether it is useful depends on something you control. A notice arrives naming a product and a version range, and the exposure belongs to an installation, so the useful inventory is keyed to installations rather than products, carries the identifiers a vendor advisory actually publishes, and adds the column almost nobody holds: what each installation is allowed to do. Sorting by capability rather than by licence cost puts the small connector holding a bank credential above the expensive reporting layer that can only read. Between the notification and a deployed fix there can be days, and finance already owns levers that work in minutes, such as taking an auto-release threshold to zero, requiring dual release, freezing bank detail changes or holding a filing before transmission. Here is what the Regulation says, read from the text, the inventory and capability tiering that makes a notice actionable, and the evidence that turns the response into a control that operated.
One meter can bill the customer and book the revenue.
Software pricing is moving from seats to meters, and the meter is now an accounting record. Deloitte’s 2026 technology predictions cite a Maxio survey finding 83 percent of AI native software companies already offering usage based pricing, and quote Gartner expecting at least 40 percent of enterprise software spend to shift toward usage, agent or outcome based pricing by 2030. Deloitte published a Technology Spotlight on outcome based pricing in agentic software on 4 June 2026, and the notable thing about it is how little new law it contains. The paragraphs have been there since the standard was written. A hosted service is usually a series of distinct service periods, which is what lets a variable fee belong to March rather than to the contract as a whole. From there one question decides everything: is the fee attributable to a single reporting period? A monthly success rate that resets can be allocated to the month it was earned in under ASC 606-10-32-40 or IFRS 15 paragraph 85. The same rate measured across a twelve month term cannot, so it becomes an estimate made at inception, constrained, spread and revisited at every reporting date. Same product, same price, same meter, one clause apart. The usage based royalty shortcut does not help, because IFRS 15 paragraph B63 confines it to a licence of intellectual property. And a contractual definition of a successful outcome turns out to be a query over an audit trail: posted with a document identifier, approvals matching the delegated authority matrix, no override, no reversal inside the agreed window. Here is the paragraph map, the four contract shapes and where each lands, the event record that can serve billing and revenue at once, and the controls that stop a late or reversed event restating a closed period.
Turn the investment policy into limits your systems can check.
Three in four organisations have a written investment policy, according to the 2026 AFP Liquidity Survey, and almost none of them can ask a system whether today’s portfolio is inside it. The gap is getting more expensive, because the portfolio is moving. The survey, fielded in March 2026 among 309 US treasury professionals, records 46 percent of organisations increasing their US cash balances, an average 83 percent of short term investment balances held in safe and liquid vehicles, the average share in bank deposits falling to 42 percent, the lowest since 2011, and the share in Treasury securities rising. More vehicles means more counterparties, more redemption mechanics and more settlement conventions, each of which the policy already has an opinion about in prose. The differences are real and specific. Institutional prime and institutional tax exempt money market funds must impose a mandatory liquidity fee once daily net redemptions exceed 5 percent of net assets, unless liquidity costs are de minimis, while government funds sit outside that trigger. FDIC insurance covers deposits to at least 250,000 dollars per insured bank, which at corporate scale is a detail rather than a protection. A repurchase agreement carries two credits, not one. The fix is ordinary engineering: give every holding an instrument record stating how it actually redeems, key every counterparty to a legal entity identifier with its parent so exposures roll up to the credit rather than to the account, express each policy clause as a limit row with a value and an effective date, and run the check before the money moves. Here is the data model, the pre trade and daily checks that sit on it, the evidence it produces, and the failure modes worth designing around.
A clean receivables aging, a much lighter credit loss estimate.
ASU 2025-05 is effective for annual reporting periods beginning after 15 December 2025 and the interim periods inside them, so for a calendar year entity it governs the allowance being built right now. It adds a practical expedient, available to every entity, that lets you assume current conditions at the balance sheet date do not change for the remaining life of current accounts receivable and current contract assets arising under Topic 606. That removes the reasonable and supportable forecast of how conditions might evolve, which the FASB itself describes as costly and complex work that generally does not move the estimate for short term assets. It also gives entities other than public business entities an accounting policy election to consider cash actually collected after the balance sheet date, so an invoice already paid needs no allowance held against it. What stays is the requirement in paragraph 326-20-30-10D to reflect conditions that already exist, such as a customer in financial distress or a loosening of credit policy, even where loss history has not caught up. The practical effect is a transfer of weight. Take the macroeconomic layer off the estimate and the aging schedule and the loss rates carry the result, and both are outputs of the order to cash stack. Example 5A in the Update is worth reading closely, because the same portfolio produces an allowance of 20,646 under the expedient alone, 21,392 when collections are considered through 1 March and 17,357 when considered through 31 May. The chosen date moves the number in both directions. Here is what the Update actually says, read from the text page by page, and the aging snapshot, cash application tie and pooling record that make the lighter estimate defensible.
When an authority asks who made a product, your system can already answer.
Regulation (EU) 2024/3015 prohibits placing or making available on the Union market, or exporting from it, any product made with forced labour at any stage of its supply chain. It applies from 14 December 2027, and the enforcement scaffolding is already switched on: member states named their competent authorities by 14 December 2025, and in June 2026 the Commission launched the Forced Labour Single Portal, published its implementation guidelines and began making its risk database public. The Regulation adds no new due diligence duty of its own. What it adds is an enforcement process that runs on facts an ERP rarely holds cleanly. In a preliminary phase, an authority asks an economic operator what it has done to identify and address forced labour risk, and the operator answers within 30 working days. If a substantiated concern remains, a full investigation follows, and the operator has to identify the products and their manufacturer, producer, product suppliers, importer or exporter within 30 to 60 working days. If the operator refuses, misses the deadline or gives incomplete information, the authority may decide on the facts available, and a ban issued in one member state is recognised and enforced across all of them for products with the same identification information from the same supply chain. Read as a systems problem rather than a policy note, the whole thing turns on one artefact most companies do not yet hold: a map from each product to the suppliers behind it, stage by stage, scored against the public risk database. Here is what the Regulation asks, how enforcement actually works, and the supply chain traceability record worth building while there is still time.
The pay report due next June is already being written, one payslip at a time.
Directive (EU) 2023/970 asks employers with 250 workers or more to report seven pay figures by 7 June 2027, and every year after that. The figures relate to the previous calendar year, which means the payroll running right now is the data that gets reported. The arithmetic is simple. Assembling the inputs is not, because the Directive defines pay as the ordinary basic wage plus any other consideration in cash or in kind, and its recitals name bonuses, overtime compensation, travel facilities, housing and food allowances, payments for attending training, dismissal payments, statutory sick pay and occupational pensions. Those live in payroll, in a pension provider, in a benefits platform and in expenses. The report also needs a pay level expressed as gross annual and gross hourly pay, quartile bands across the whole workforce, and categories of workers grouped on skills, effort, responsibility and working conditions. Where a category shows a gap of at least 5 percent that is not justified on objective gender-neutral criteria and is not remedied within six months, a joint pay assessment follows. The transposition deadline of 7 June 2026 has passed and most member states missed it, so national timetables now vary while the reporting content stays common. Here is what the Directive actually asks, why the hard part is a join rather than a calculation, and the pay record worth building while the reference year is still running.
Which payments to customers are really a discount on your revenue?
A rebate, a slotting fee, a platform credit and a co-op advertising reimbursement all leave a company the same way, through accounts payable, and some of them are not costs at all. Under Topic 606 an entity accounts for consideration payable to a customer as a reduction of the transaction price, and therefore of revenue, unless the payment buys a distinct good or service that the customer transfers back. The scope of that rule has been argued over for years, and the FASB is about to propose an answer. In January 2026 the Emerging Issues Task Force received an agenda request about when payments made on behalf of a customer, or to a customer of a customer, fall inside it. The Task Force discussed the question on 23 June 2026 and recommended a framework built on an explicit or implicit promise and on the idea of an in-substance price concession. The Board added the project to its technical agenda in August 2026, and its technical agenda overview, revised on 9 September 2026, lists an exposure draft for the fourth quarter. Read as a systems problem rather than a disclosure question, this turns on facts most ledgers hold loosely: whether the payee sits on the revenue side of the house, which contract the payment belongs to, whether anything distinct came back, and what it was worth. Here is what the rule says today, what the Task Force recommended, and the payments-to-customers record worth building before the exposure draft lands.
Every sale inside the group needs to know which boundary it crossed.
Inside a group, some profit is real and some is the group selling to itself, and a consolidation engine tells the two apart by looking at the counterparty. A sale to a subsidiary is eliminated in full, because IFRS 10 reports a parent and its subsidiaries as one economic entity. A sale to an associate is treated differently: paragraph 28 of IAS 28 lets an investor recognise the gain only to the extent of unrelated investors’ interests, so part of it is held back until something releases it. The IASB is close to finishing a rewrite of that second rule. Its exposure draft on the equity method, published on 19 September 2024, proposed recognising gains and losses in full on every upstream and downstream transaction with an associate. Through 2026 the Board redeliberated toward something more nuanced: an accounting policy choice between full and restricted recognition, transfers of a business always recognised in full, a matching change to IFRS 10, and disclosure that depends on which way a company chose. The next milestone on the project is the final amendments. Read as a systems problem rather than an accounting election, all of it rests on data most groups hold loosely: which counterparty is a subsidiary and which is an associate, which way the goods moved, what was actually transferred, and the running balance of any gain still held back. Here is what the Board has decided so far, why the boundary of the reporting entity is the idea that makes the rest cohere, and the intercompany transaction record worth building before the amendments land.
Let the cash line say what it is made of.
On any balance sheet, cash and cash equivalents looks like a single, settled number, but it is really a small portfolio: an operating bank balance, a money market fund, a Treasury bill, a slice of commercial paper, and now, for a few companies, a stablecoin. On 18 August 2026 the FASB proposed to make that portfolio visible. Its exposure draft on the statement of cash flows, Topic 230, would require an entity to disclose every year the significant components of what it presents as cash equivalents and the amount of each, and it adds examples showing when a digital asset such as a stablecoin qualifies. The proposal leaves the definition of a cash equivalent untouched: a short-term, highly liquid investment that is readily convertible to a known amount of cash and so near its maturity that a change in interest rates barely moves its value, generally an original maturity of three months or less to the holder. What changes is that the make-up of the line, long a quiet accounting policy, now has to be shown component by component. Read as a systems problem rather than a disclosure note, the same instrument-level record that answers the FASB also feeds the balance sheet total, the statement of cash flows, and treasury’s own view of the cash it can actually reach. Here is what the proposal asks, why naming the parts of the cash line is an opportunity rather than a burden, and the cash classification record worth building before the first disclosure is due.
A routine distributor’s arm’s length return now comes from a shared table, and clean ERP data is what earns it.
For years, pricing a routine distributor inside a multinational group meant the same expensive ritual: pull a set of comparable companies, run a benchmarking study, defend the range, and do it again when a tax authority in another country disagreed. The OECD published a different path on 19 February 2024. Its report, Pillar One Amount B, sets out a simplified and streamlined approach that prices baseline marketing and distribution using a fixed matrix of returns rather than a fresh study each year, and it has been built into the OECD Transfer Pricing Guidelines as an annex to Chapter IV. Jurisdictions can choose to apply it for fiscal years beginning on or after 1 January 2025, and the United States said in Notice 2025-04 that its taxpayers may elect it from the same date. The return a qualifying distributor should earn is read from a table, and which cell of that table applies is decided by data a finance team already owns: the industry of the goods it distributes, its operating expenses against revenue, and its net operating assets against revenue. Read as a systems problem rather than a tax filing, this is a distributor pricing record a finance team can own. Here is what Amount B actually asks, why a predictable return is an opportunity rather than a constraint, and the data worth building so every in-scope entity can show which cell it lands in and why.
A French supplier’s invoice now arrives as structured data, and the platform that carries it also reports it.
For most of its life an invoice between two French businesses was a PDF in an email or a sheet of paper in the post, and the tax office saw it only if it asked. That changed on 1 September 2026. France started its business-to-business e-invoicing and e-reporting reform on the date fixed by the loi de finances pour 2024, and the first obligation is plain: every business established in France must be able to receive a structured electronic invoice through an approved platform, a plateforme agréée the State has registered. Large and mid-sized enterprises must also issue every domestic invoice that way from the same date, with smaller businesses following on 1 September 2027. The same platform that carries the invoice hands the tax administration the data on it, and that data goes on to pre-fill the VAT return, so a compliance step and a clean accounts payable feed turn out to be the same piece of work. Read as a systems problem rather than a filing chore, this is a reception, issuance, and reporting record a finance team can own. Here is what the mandate actually asks, why a structured invoice through a platform is an opportunity rather than a burden, and the record worth building so every French entity can show it is ready.
A stolen access token can be worthless to the thief who took it.
Finance no longer moves through a bank portal and a file upload. It moves through APIs: an ERP calling a bank to fetch statements and send payments, a treasury system pulling balances, a payments provider posting settlement data. Each of those connections carries authority to move money or read sensitive records, so the security of the connection is a finance control, not an IT footnote. The recognized bar for it now has a name and a finished specification. The OpenID Foundation published the FAPI 2.0 Security Profile as a final standard on 22 February 2025, and it sets what a financial grade API connection should look like. Its central move is simple to say: access tokens are sender constrained, bound to the client they were issued to, so a token copied from a log or a breached server is useless to whoever holds it. Around that it requires pushed authorization requests, PKCE, and protections against request tampering and mix up attacks, and its security is formally analysed against a defined attacker model. Read as a systems problem, this is a connection register a finance team can own. Here is what FAPI 2.0 actually requires, why a sender constrained token changes the economics of a stolen credential, and the record worth building so every API connection can show the profile it meets.
When you close the books, can every balance sheet account prove what it holds?
Financial close and reporting is still one of the most common places a company reports a material weakness, KPMG found in its review of the latest annual filings, and the reason is often quiet: the numbers on the balance sheet were never tied back to independent support. A balance sheet reconciliation is the control that does that tying. It proves that the balance in the general ledger equals what an outside record says should be there, and it explains, owns, and ages every difference. Read as a systems problem rather than a month end chore, the reconciliation stops being a spreadsheet someone rebuilds each period and becomes a governed record: the account, its risk tier and cadence, the general ledger balance, the independent support, each reconciling item with an age and an owner, a preparer and a separate reviewer, and a roll forward into the next period. The regulators who define internal control put the period-end financial reporting process, with its reconciliations and reviews, at the center of what an auditor must evaluate, and the same record that satisfies them makes the close faster and the evidence ready before anyone asks. Here is what a reconciliation actually proves, how substantiation differs from transaction matching, and the close record worth building so every balance sheet account can explain itself.
Last year’s payroll already knows who must make their catch-up on a Roth basis this year.
For two years the rule sat behind a transition period, and that period covered only 2024 and 2025. Starting with catch-up contributions made in 2026, an employee whose FICA wages from you last year were above the Roth catch-up wage threshold, 150,000 dollars measured on 2025 wages, must make their catch-up on a Roth basis, and the IRS finalised the rules in September 2025. Read as a payroll problem rather than a plan notice, the whole determination turns on one number your systems already produce: the prior year Box 3 wages an employee earned from you, measured per employer rather than across a career. If that number is above the line the catch-up is Roth, if the employee had no wages from you last year they are not subject, and if the plan has no Roth account a subject employee cannot catch up at all. The same wage figure that decides this also fills Box 3 on the W-2 and helps set who counts as highly compensated, so a small amount of data plumbing turns a compliance date into a clean lookup. Here is who the rule reaches, how the prior year wage test actually works, and the payroll record worth building so the right catch-up lands in the right source without anyone having to remember.
Let the purchase order and the goods receipt vouch for every invoice.
An invoice is the one document in a purchase that a stranger can send you, and in 2025 that is exactly where the money goes. The FBI Internet Crime Complaint Center recorded business email compromise as the second largest source of reported losses, more than three billion dollars across 24,768 complaints, with the funds leaving mostly by wire transfer or ACH, and it warns that generative tools now make a convincing fake request cheaper and easier to produce. The oldest control in accounts payable answers that risk. A three-way match will not pay an invoice unless it agrees with two records your own operations create, the purchase order that authorized the buy and the goods receipt that confirms what actually arrived. A fabricated invoice or a spoofed supplier email can forge the third document, never the first two. Read as a systems problem, the match is only as strong as the data behind it: a real purchase order, a timely goods receipt with quantity and date, tolerances set on purpose, and a vendor master whose bank details cannot change without a controlled review. Build that and the same records that stop a bad payment also give a clean goods received not invoiced accrual, a faster close, and evidence an auditor can read. Here is what the three-way match actually checks, why the order and the receipt are the records worth trusting, and the purchase-to-pay record worth building so a payment is a lookup rather than a leap of faith.
A payment can leave the books the moment you can no longer stop it.
The IASB amended IFRS 9 and IFRS 7 to settle how the derecognition and classification rules work for financial instruments, and the changes take effect for annual reporting periods beginning on or after 1 January 2026, with earlier application permitted. Two of them reach straight into everyday finance. The first sets the derecognition date for a financial liability as the settlement date, and adds an accounting policy election to treat a payable as discharged before settlement when it is paid in cash through an electronic payment system, but only when the company has no practical ability to withdraw, stop, or cancel the instruction, no practical ability to access the cash, and settlement risk through that system is insignificant. The second clarifies when a loan or receivable with a contingent feature, including a rate that moves with a borrower carbon emissions target, still passes the solely payments of principal and interest test. Read as a systems problem, both turn on data a finance team already owns: the exact status of a payment instruction, the electronic payment system it runs on, and the contractual terms attached to a financial asset, captured as governed fields rather than argued at close. Here is what the amendments actually say, why the derecognition date and the election matter for accounts payable and the cash ledger, and the record worth building so the accounting reads from the payment rather than from memory.
The checkout barcode is about to carry the batch number and the expiry date.
Retail is moving from the striped one dimensional barcode to a two dimensional one, a QR code or a DataMatrix, and industry has set a date for it: retail checkout systems should be able to scan and process a 2D barcode by the end of 2027, an effort GS1 calls Sunrise 2027. The one requirement to make checkout work is that the till reads the same product number, the GTIN, that the old barcode carried. The opportunity sits in what else the 2D barcode can carry in the same scan: the batch or lot number, the expiration date, and a serial number, each defined by a GS1 Application Identifier. For a finance and operations team that is not a checkout story, it is an item master story. Read as a systems problem, the product record stops holding only an identity and starts holding the attributes that decide inventory valuation, recall reach, and returns, captured at the scan rather than keyed later or missing. Here is what Sunrise 2027 actually requires, what the extra data unlocks for finance, and the item master record worth building so a near expiry write down or a recall is a query rather than a stock count.
Instant payments now move ten million dollars in seconds, and the payment run is where you build the confidence to send.
The Federal Reserve raised the FedNow Service transaction limit from one million dollars to ten million dollars, effective November 2025, and named corporate treasury, payroll, vendor payments, and commercial real estate as the high value uses it now supports. Instant payments change more than speed. A FedNow credit settles in near real time, the network runs every day of the year, the receiver gets the funds the moment settlement is confirmed, and a completed credit has no reversal the sender controls. That moves the checks a company relies on to the seconds before a payment leaves: a verified beneficiary account, a sanctions and duplicate screen, and a sending limit set on purpose per counterparty and per segment. Read as a systems problem, the payment run stops being an overnight file and becomes a governed control point, and the same instant confirmation that proves the money landed also closes the cash application it feeds. Here is what changed, why final and always on rewrites the control model, and the payment run record worth building so a ten million dollar send is a lookup rather than a leap.
Your cash and receivables can prove themselves from the outside.
A new PCAOB standard, AS 2310, The Auditor’s Use of Confirmation, is in force for audits of fiscal years ending on or after 15 June 2025, so the calendar year 2025 financial statements being audited right now are the first under it. It reframes audit evidence for cash and receivables around a knowledgeable external source, and it gives two roads to that evidence: a confirmation the auditor controls from selecting the items to receiving the response, or the auditor directly accessing information the external source maintains, such as reading a bank balance on the institution’s own secure site. Read as a systems problem, both roads run on data a finance team already owns: accurate counterparty master data so requests reach the right source and responses return to the auditor, a confirmation channel the company cannot override, and preserved third party documents behind each receivable. Here is what the standard asks paragraph by paragraph, why cash and accounts receivable get their own rule, and the confirmation readiness record worth building so a clean external trail closes the audit faster and the evidence is a lookup rather than a scramble.
Some sales are yours to book in full, and some are only the fee for arranging them.
When another party helps deliver something to your customer, one question decides how much revenue you report: did you control the good or service before it reached the customer? If you did, you are the principal and you book the gross amount. If you did not, you are the agent and you book only your fee for arranging it. That single answer can move reported revenue by the size of the third party cost, and it is asked for each specified good or service, so a single contract can be principal on one line and agent on another. The post-implementation review of IFRS 15, concluded on 30 September 2024, found the standard working as intended, and still singled out this control assessment as one of the few application matters worth carrying to the board next agenda consultation. The same test governs US GAAP under Topic 606. Read as a systems problem, gross or net stops being a memo re-argued every quarter and becomes a governed attribute: a revenue role per specified good or service and flow, backed by the three control indicators captured as evidence, with the gross and net amounts held as separate fields. Here is what the standard asks, why marketplaces, resellers, and bundled services find it hard, and the revenue record worth building so the presentation is a lookup with an audit trail.
How busy a year is baked into your overhead rate?
Every standard cost carries a quiet assumption about how busy a normal year is, and right now that assumption is under pressure. The Federal Reserve put capacity utilization at 76.3 percent for July 2026, about three points below its long run average, with manufacturing lower still. Both IFRS and US GAAP say the same thing about that gap: fixed production overhead is allocated to units on the basis of normal capacity, the per unit charge is not raised because a plant ran quiet, and the overhead left unabsorbed is an expense of the period rather than a cost that rides into inventory. IAS 2 also asks that standard costs be reviewed regularly and revised in the light of current conditions. Read as a systems problem, the normal capacity figure buried in every overhead rate becomes a governed number worth owning: set on purpose, versioned, tied to the volume variance it produces, and checked at close so under absorbed fixed overhead reaches the income statement. Here is what the two standards require, why the single blended overhead rate most systems carry is the thing that quietly capitalizes a slow quarter, and the cost record worth building so the roll, the variance, and the close read from one normal capacity.
Book the rate you could actually get, and keep the working.
An IFRS amendment that took effect for annual periods beginning on or after 1 January 2025 changes a quiet assumption inside every multicurrency ledger: that the rate on the feed is a rate you could actually trade at. IAS 21 now asks a company to decide, at each measurement date and separately for each purpose, whether a currency is exchangeable into another at all, and when it is not, to estimate the spot rate an orderly transaction would use under prevailing conditions, then disclose how it got there. The first full year statements applying this are being prepared and audited through 2026. Read as a systems problem, it turns one hard judgment into a governable data object: an estimated rate distinct from the feed rate, tied to a measurement date and a purpose, carrying its method, its inputs, and the four disclosures the standard asks for. Here is what the amendment requires, why the single rate per currency pair that most systems hold is the thing that breaks, and the exchange rate record worth building so the revaluation and the note read from the same governed number.
The place your research happens decides how fast you deduct it.
New Internal Revenue Code section 174A, added by the One Big Beautiful Bill Act, lets a company deduct its domestic research costs in the year they are paid or incurred again, for tax years beginning after 31 December 2024. Research performed abroad stays under section 174 and writes off over fifteen years. The whole difference between an immediate deduction and a fifteen year one turns on one attribute of every research dollar: where the work was actually done, tested by the geographic rule in section 41(d)(4)(F). Rev. Proc. 2025-28 adds the elections, the method change mechanics, and a way to release the 2022 to 2024 costs stranded on the balance sheet. For a finance team that reads as one instruction: capture place of performance on the cost record, split the pool from it, and keep the prior year schedule ready to draw down. Here is what changed and the research cost model worth building so the return is a query rather than a reconstruction.
One marker on every account is the whole of year one.
Poland now requires corporate income tax payers to keep their accounting books electronically and file them as a structured data file, the JPK_CIT, and the first of those files, JPK_KR_PD, fell due for the largest companies on 31 July 2026. The load bearing detail is small. In the first covered year the rules let a first wave company leave out four of the five new data elements, so the only new content most of them had to add was an identifier from a Ministry of Finance dictionary on every account in the chart of accounts. That turns the chart of accounts into a governed master data object with an external schema: mapped once, owned by someone, and versioned as it changes. Here is the timetable, exactly what the file asks for, and the account to marker mapping worth building as master data rather than rebuilding every filing season.
The barrel in the tank and the price on the screen.
For years a company can carry its physical commodity inventory at the lower of cost or net realizable value while the derivatives it uses to manage price risk sit at fair value, so earnings swing for reasons that have little to do with the economics. The FASB put Accounting for Commodities on its agenda on 4 February 2026 and, per its technical agenda revised 20 August 2026, expects a proposed Update in the fourth quarter that would let a defined set of entities elect to measure tangible commodity inventory at fair value. Whatever the final scope, the work that makes a finance team ready, and that pays off today, is an inventory subledger that carries a governed market price for each lot next to its cost, records the election at the level it is made, and maps the remeasurement to a named income statement line. Here is what the Board is building, why the mismatch exists, and the two-basis inventory data model worth having in place before the exposure draft lands.
Does your segment note read from the same numbers your CODM sees?
How ASU 2023-07 helps controllers, external reporting teams, FP&A, and finance systems owners turn the significant expense principle, the other segment items residual, interim disclosure, and the single reportable segment scope into one governed mapping the CODM package and the audited footnote can both read from.
Give government grants their own subledger.
How ASU 2025-10 and the disclosure rules already in force help controllers, technical accounting leads, fixed asset teams, and finance systems owners design grant condition tracking, the probable assessment, the deferred income and cost accumulation elections, recapture terms, and the audit evidence behind them.
Stablecoin acceptance now has a timetable, and the redemption right is where the ledger design starts.
How the GENIUS Act timetable and the Treasury rulemaking of 18 August 2026 help treasurers, controllers, technical accounting teams, and finance systems owners design stablecoin acceptance policy, issuer master data, redemption evidence, cash application, and the classification behind the balance sheet line.
Full first year expensing on a new plant comes down to how well you can describe the space.
Section 168(n) lets a company deduct 100 percent of the basis of a new production building in the year it is placed in service, and IRS Notice 2026-16 explains how. The qualifying portion is measured by physical space, so the production floor and raw material receiving count while offices, parking, sales, research and finished goods storage do not. Basis is split by square footage, cost segregation data, engineering plans, process diagrams or construction invoices, and never by headcount or hours. The election is made property by property on a timely filed return and can be revoked only through a private letter ruling. Here is what the notice requires, the fields a fixed asset register needs before the election is filed, and the ten year monitoring that follows it.
IFRS 19 retires the second set of books, one subsidiary at a time.
IFRS 19 takes effect on 1 January 2027 and lets an eligible subsidiary publish a much shorter set of notes while keeping full IFRS recognition, measurement and presentation. The UK Endorsement Board adopted it in May 2026, and its own assessment puts roughly 78,000 subsidiaries of London-listed groups inside scope, 57,000 of them domiciled outside the UK. The election is made entity by entity and tested again at every period end, which makes it a dated field in the entity master rather than a one-off accounting decision. Here is what the standard changes, why the group consolidation pack stays exactly the same size, the two data grains that a move away from FRS 101 will expose, and the entity register worth building before the first election is made.
The reasons customers give for paying late read like a design brief for order-to-cash.
Four regional surveys published in 2026 asked thousands of receivables managers the same question: why do your business customers pay late? Customer cash flow comes first in every region, and it is the one answer a supplier cannot design around. The next three are different. Internal approval delays, complex payment processes, and goods or services not as agreed all describe friction between the invoice and the person who has to approve it, and every one of them is decided by choices a supplier makes before the invoice is sent. Meanwhile global payment terms have been flat since 2022, so the spread between suppliers is not a macro story. Here is what the surveys found, how each named cause maps to a specific field, rule, or gate in the order-to-cash chain, and the two measures worth building toward.
The connection between an AI agent and your ERP is an interface you already know how to govern.
The Model Context Protocol has become the ordinary way an AI agent reaches a business system, and ERP vendors now ship MCP servers over the ledger itself. In May 2026 the NSA published its design considerations for the protocol, and the most useful sentence in it is the plainest: the protocol does not enforce your controls. Authorization is optional. Role permissions are not exchanged. Audit logging is left to whoever built the server. None of that is a reason to wait, because the controls a finance team needs sit one layer up, in the ERP role model, the token exchange, and the interface register. Microsoft and SAP have both published designs that put them there. Here is what the guidance actually says, where the protocol stops and your ERP starts, and the register that makes an agent posting into the ledger as explainable as any other interface.
SAP’s extended maintenance window buys enough time to write down what finance actually customised.
Mainstream maintenance for SAP Business Suite 7 core applications, SAP ERP 6.0 among them, runs to the end of 2027. Optional extended maintenance then runs from the start of 2028 to the end of 2030 for two percentage points more on the maintenance basis, and the DSAG Investment Report published on 26 February 2026 found that almost half of the members still investing in SAP ECC plan to move by the end of 2030, which means paying for that window. So the runway is real and it is measured in years rather than months. The most useful thing a finance team can do with the early part of it has nothing to do with picking a target release. SAP’s own Custom Code Migration Guide asks for at least a year of production usage data before anyone scopes the work, and it says exactly why: so that quarter and year ending functionality is considered. Finance code is the code that runs four times a year, or once. Here is what SAP has published about which finance objects change, why a read still works where a write does not, and how to build the extension register that makes the whole decision defensible.
Brazil’s IBS and CBS classification code belongs in the item master, and 2026 is the year to put it there.
Two things happened in Brazil within five days of each other. On 30 July 2026 the Receita Federal and the Comitê Gestor do IBS set the start dates for mandatory issuance of electronic fiscal documents carrying the new IBS and CBS fields, beginning with the NF-e and NFC-e on 3 August 2026 and running through to the Duimp on 1 January 2027. On 4 August 2026 version 1.51 of Nota Técnica 2025.002 struck the matching production rejection rule and moved it to a future date. The obligation is live and the gate that would enforce it is not, which is the most useful position a finance systems team has been handed in a while. The field at the centre of it is a classification code that points at a specific article of Lei Complementar 214/2025, and every item on every line now needs one. Here is what the two publications actually say, what the published classification table contains, and how to govern the code as item master data during the year that was designed for exactly that.
Fedwire is adding a Sunday. The payment calendar is where the work starts.
The Federal Reserve Board has decided that the Fedwire Funds Service and the National Settlement Service will run 22 hours a day, six days a week, Sunday through Friday including weekday holidays, with the Reserve Banks expected to implement it in 2028 or 2029. The extra settlement days are the headline. The part that reaches finance systems is quieter: the word "business day" currently resolves to one shared answer, and it is about to resolve to several. Fedwire will treat Sunday as a business day. Regulation CC will still exclude Saturdays, Sundays and ten named holidays. Each bank decides for itself whether Sunday is one of its funds-transfer business days and where its cutoff times sit. Contracts that define the term by pointing at Fedwire will move on their own. Here is what the Board actually decided, which calendars stop agreeing, and how to turn the payment calendar from a copied holiday table into governed data while there is a comfortable runway to do it.
Tariff refunds arrive by entry number and land in the ledger by cost layer.
The Supreme Court held on 20 February 2026 that IEEPA does not authorise the President to impose tariffs, and US Customs and Border Protection now runs a refund path called CAPE inside the ACE Portal. Filing is a CSV of entry numbers, which makes it look like a customs errand. It is really an inventory costing exercise: the duty was capitalised into the cost of goods that have mostly been sold since, so the refund has to be routed between the balance sheet and cost of sales layer by layer. CBP also nets each entry, offsets unpaid debts, and pays one consolidated sum per recipient and liquidation date, so the cash that lands will not match the claim you calculated. Here is how the refund is actually computed, what a CAPE Declaration certifies, where the money belongs in the ledger, and the cost data that decides how much of it you can explain.
Britain’s payment reporting rules reward the teams that keep three dates straight.
Large UK companies now have to put their supplier payment performance in the directors’ report, for financial years beginning on or after 1 January 2026. That year is already running, which means the numbers are being created right now out of three dates that most accounts payable systems treat as secondary: the day the invoice was received, the payment period in the individual contract, and the day the supplier actually got the money. None of them is the invoice date, the posting date, or the payment run date. The Commercial Payments Bill introduced in May 2026 then attaches a 60 day ceiling, statutory interest at 8 percent above base rate, and enforcement to the same fields. Here is what the regulation actually asks for, how it lines up against the twice-yearly portal filing, the data model that satisfies both from one source, and what a finance team can fix while the year is still open.
Australia’s tax office showed its working on Payday Super, so payroll can check every payday first.
Australia switched superannuation guarantee from a quarterly payment to a per-payday one on 1 July 2026, and the deadline is now measured on the day the money lands in the fund rather than the day you send it. The useful part is that the ATO published the exact calculation it will run: take the qualifying earnings for a payday as the difference between two Single Touch Payroll year-to-date figures, apply 12 percent, and compare the result against the amount and date the super fund reported. Both of those facts already sit in your own payroll and banking records, so the same reconciliation can run in-house on the eighth business day. The administrative uplift table then puts a published price on how quickly you find your own exceptions. Here is the deadline calendar, the pay-code question worth settling, the per-payday reconciliation, and the control design a payroll and finance team can build now.
Equity from a customer stays revenue until your side of the deal is done.
FASB issued ASU 2025-07 on September 29, 2025, and it takes effect for annual periods beginning after December 15, 2026, which is January 1, 2027 for a calendar-year company. It settles a question that had been answered several different ways: when a customer pays you in warrants or shares, that consideration stays inside Topic 606 until your right to receive or retain it becomes unconditional, and only then does it move to equity securities or derivatives accounting. The same Update also pulls contracts whose settlement depends on one party’s own operations, such as a regulatory approval or a product development milestone, out of derivative accounting entirely. Both changes turn on facts your contract and revenue records already hold. Here is the contract register, the handoff event, and the control design a finance team can build before adoption.
Data that reaches your ledger untouched is the cheapest audit evidence you can hand over.
The PCAOB’s technology-assisted analysis amendments apply to audits of fiscal years beginning on or after December 15, 2025, so a calendar-year company is inside the first year in scope right now. The part that reaches finance is paragraph .10A of AS 1105: when a company hands its auditor information it received from an outside source, the auditor has to understand how that information was received, maintained, and processed on the way in, and then either test it or test the controls over it. The Board turned down a one-year deferral request and answered with a policy statement and staff examples instead. Those examples read like an integration diagram. A vendor invoice stored exactly as it arrived needs no separate testing. A bank feed converted and posted into the ERP does. Here is the source inventory, ingestion register, and control design a finance team can build before its first year-end under the rule.
Without a mandate behind it, the new software bill of materials baseline still belongs in vendor contracts.
On July 29, 2026, CISA, the NSA, the FBI, and fifteen international partner agencies published the 2026 Minimum Elements for a Software Bill of Materials, the first full refresh of the baseline NTIA set in 2021. It adds component hashes, licenses, and an explicit field for unknown data, and extends scope to open source, AI, and SaaS. The mandate behind the old baseline is gone, since OMB rescinded the government-wide attestation requirement in January 2026 and left SBOM requests to each agency and each buyer. That leaves the artifact itself, not a rule, as the reason to update it. Here is the vendor master data field, contract clause, and audit-evidence design a procurement or finance team can build now.
Bringing every lease onto the balance sheet is the easy half of FRS 102’s periodic review.
The Financial Reporting Council’s Periodic Review 2024 amendments to FRS 102 reached their principal effective date on January 1, 2026: an on-balance-sheet right-of-use model for lessees, and a five-step revenue recognition model aligned to IFRS 15. Getting that entity-level accounting right is the well-documented half of the work. The less-documented half is a Section 11 and 12 change that ties a subsidiary’s own accounting policy to the group’s consolidated policy, plus new transition disclosures, both of which turn a UK or Irish group’s first close under the new standard into a consolidation-governance project. Here is the policy-consistency and transition-election register a group finance team can build once and reuse.
A chosen technical operator sets a 2027 target treasury teams can build toward.
Nexus Global Payments named PayNet and NETS as the Nexus Technical Operator on February 9, 2026, moving the Bank for International Settlements-originated Project Nexus from blueprint to build for a six-market instant-payment interlink spanning India, Malaysia, the Philippines, Singapore, Thailand, and Indonesia, with a 2027 target go-live. A single connection point changes what beneficiary, FX, and compliance data treasury needs on file. Here is the master-data and control design a finance team can start now, well ahead of go-live.
A sanctions list update leaves the vendor file one afternoon to catch up.
The EU adopted its 21st Russia sanctions package on July 23, 2026, the largest single batch of listings in four years at 218 names, ten days after two smaller list amendments took effect the moment they were published. Each new name creates an asset freeze obligation with no phase-in period, while other measures in the same package carry their own later deadlines. Here is the screening-event record and rescreen trigger design that turns a publication-day list change into routine work instead of a scramble.
SWIFT’s 2026 back-office control puts a name on the data path to your ERP.
SWIFT’s Customer Security Controls Framework v2026 makes Control 2.4, Back Office Data Flow Security, mandatory for the July to December 2026 attestation window, extending the compliance perimeter past the SWIFT secure zone into the connections that reach ERP, treasury, and reconciliation systems. Most institutions that failed their first 2025 assessment closed the gap through remediation. Here is the flow register and control design that gets a finance team ready before the window closes.
Bank regulators just previewed the model inventory AI governance will require.
On April 17, 2026 the Federal Reserve, OCC, and FDIC issued SR 26-2, replacing SR 11-7 with a materiality-based approach to model risk management, and stated plainly that generative and agentic AI models sit outside its scope for now. A request for information on AI models is coming. Here is the inventory finance teams can build with the tiering method already in hand, before that request lands.
Does your consolidation model know which associates just went fair-value eligible?
On June 26, 2026 the IASB issued targeted amendments to the IAS 28 fair value option, widening it beyond venture capital and fund structures to any entity with a specified main business activity of investing. The amendments take effect alongside IFRS 18 for periods beginning January 1, 2027, and open a one-time window to move an associate or joint venture off the equity method. Here is the consolidation register finance teams can build to track the decision.
The federal vendor record is splitting in two, and procurement should get ahead of it.
FAR Case 2026-001, published June 23, 2026, would split the federal vendor record in two: entity-level data staying in SAM.gov, and procurement-specific certifications moving into each solicitation. The comment period closed July 23, 2026 with no final rule yet. Here is the supplier record procurement and ERP teams can build now, before the split becomes mandatory.
California's climate deadline shift opens a runway for real emissions data systems.
CARB pushed the year-one SB 253 Scope 1 and 2 reporting deadline from August 10 to November 10, 2026, and previewed the five Scope 3 categories and the assurance standards coming in 2027. Here is the emissions data register finance and reporting teams can build in the extra time, instead of scrambling before the new date arrives.
Every bank API connection needs an owner of record.
The Financial Data Exchange standard already covers permissioned consumer and business bank data, and 114 million accounts flow through its API today, even though the CFPB's Section 1033 rule sits enjoined and New York's small-business data access bill is still in committee. Here is the connection register finance and treasury teams need to govern bank API access as consent, not shared credentials.
Every generative AI capability in finance now maps to a specific control.
COSO published "Achieving Effective Internal Control Over Generative AI" on February 23, 2026, the first standard-setter guidance mapping GenAI capabilities like automated reconciliation and workflow orchestration to the five components of the Internal Control Integrated Framework, through a six-step govern-to-monitor roadmap.
Optional semiannual filing raises the bar on quarterly-grade close evidence.
The SEC's proposed Form 10-S would let public companies elect semiannual filing over quarterly Form 10-Q reports. Practitioner analysis is consistent that the disclosure committee, ICFR, and close evidence trail behind those filings still need to run close to a quarterly rhythm either way.
Better line-item data, lower card interchange costs.
Visa's Commercial Enhanced Data Program and Mastercard's stricter unit of measure rules turn commercial card interchange into a data-accuracy test in 2025 and 2026, and the fields they check already live on the ERP order and invoice line.
A single FASB test decides which entity's ledger survives a merger.
FASB ASU 2025-03 removes the rule that a VIE's primary beneficiary is always the accounting acquirer, opening the door to reverse acquisitions of VIEs for periods beginning after December 15, 2026, and turning the determination into a control finance and ERP teams need to design for.
New supplier onboarding increasingly starts with one Peppol identifier.
How the Peppol network four-corner model, now past 4.5 million registered participants, turns the participant identifier and access-point choice into a master-data and integration-architecture decision for procurement, AP, and AR teams.
Request-for-payment data closes the last gap in cash application.
How request-for-payment messaging and higher RTP and FedNow instant-payment limits help CFOs, controllers, AR leaders, and ERP buyers automate cash application, cut unapplied cash, and redesign collections around irrevocable, same-day settlement.
Verified organizational identity can now anchor your counterparty master data.
How CFOs, controllers, heads of procurement, and ERP buyers can treat verifiable organizational identity (the GLEIF vLEI and the EU Digital Identity and Business Wallet framework) as governed, cryptographically verifiable master data across supplier and customer onboarding, authorized-signatory records, payment authenticity, and audit evidence.
When payments carry contract identity, quarterly transparency becomes routine.
How CFOs, financial controllers, heads of accounts payable, and ERP buyers can carry contract identity through invoice, payment run, and remittance so quarterly public payment publication under section 70 of the UK Procurement Act 2023 becomes a routine extract rather than a reconciliation project.
What finance teams can build with the AI Act's extra sixteen months.
How CFOs, controllers, heads of internal audit, and ERP buyers can use the sixteen months between the AI Act transparency date and the deferred high-risk deadline to build an AI inventory, a deployer control set, and audit evidence for the AI already running inside finance.
Make the first Pillar Two filing the start of a standing entity data pipeline.
How CFOs, group controllers, tax leaders, and ERP buyers can turn the first GloBE Information Return into a standing entity, ownership, and jurisdiction data pipeline before the 15-month filing cadence and the end of the transitional safe harbour arrive.
Tips, overtime, and the payroll data model the 2026 W-2 expects.
How CFOs, controllers, payroll leaders, and ERP buyers can build the earnings classification, occupation coding, and evidence trail behind the new Form W-2 box 12 codes TP, TT, and TA for tax year 2026.
Treasury teams can make hedge accounting evidence flow with the business.
How FASB ASU 2025-09 helps CFOs, controllers, treasurers, and ERP buyers connect hedge designation, forecasted transactions, choose-your-rate debt, commodity exposure, FX debt, effectiveness testing, and audit evidence.
CBAM brings carbon-cost clarity into ERP landed-cost workflows.
How the EU Carbon Border Adjustment Mechanism helps CFOs, controllers, import teams, and ERP buyers connect supplier emissions data, customs validation, certificate prices, landed cost, accruals, and audit evidence.
EUDR readiness turns supplier origin data into procurement control leverage.
How the EU Deforestation Regulation helps CFOs, controllers, procurement leaders, and ERP buyers turn supplier origin data, due diligence references, product scope, risk ratings, customs handoffs, and audit evidence into a practical finance workflow.
ASU 2025-05 gives receivables teams a faster evidence loop.
How FASB ASU 2025-05 helps CFOs, controllers, revenue leaders, and ERP buyers turn current receivables, contract assets, collections activity, aging, credit-loss estimates, and audit evidence into a cleaner close workflow.
Income tax disclosure readiness starts with jurisdiction-grade ERP data.
How ASU 2023-09 helps CFOs, controllers, tax leaders, and ERP buyers turn jurisdiction data, cash tax payments, rate-reconciliation categories, close evidence, and audit support into a reusable finance control asset.
SEC filing access can become a stronger finance control layer.
How EDGAR Next helps CFOs, controllers, disclosure teams, and ERP buyers turn filer roles, annual confirmations, API tokens, delegated agents, filing status, and close evidence into a cleaner SEC reporting workflow.
ERP portability is becoming a finance operating advantage.
How the EU Data Act helps CFOs, controllers, finance operators, and ERP buyers turn finance data exports, exit evidence, lineage, retrieval windows, deletion proof, and vendor selection into practical operating leverage.
Ten-second euro payments make payment runs a stronger control point.
How the EU Instant Payments Regulation and Verification of Payee help CFOs, controllers, treasury teams, and AP operators redesign vendor bank master data, payment release, bulk files, exceptions, cash visibility, and audit evidence.
The 2026 1099 reset gives AP teams a filing-ready vendor data model.
How the 2026 IRS information-return transition helps CFOs, controllers, and AP teams turn W-9s, TIN matching, backup withholding, thresholds, IRIS filing, corrections, and audit evidence into a stronger ERP workflow.
Environmental credit accounting now has a cleaner ERP control map.
How FASB ASU 2026-02 and ASC 818 help CFOs and controllers turn environmental credits, planned use, compliance obligations, valuation, disclosure, and audit evidence into a practical ERP workflow.
Finance AI agents can give ERP teams a stronger evidence loop.
How CFOs, controllers, and ERP buyers can turn finance AI agents into controlled workflows with scoped permissions, policy gates, human review, observable tool calls, audit evidence, and practical rollout metrics.
The UK accounts-filing workflow finance teams can make software-ready now.
How the UK Companies House 2028 software-only iXBRL accounts filing change helps finance teams build cleaner close evidence, statutory reporting mappings, validation controls, approvals, agent handoffs, and filing records.
Structured payment data gives finance teams a cleaner treasury control loop.
How ISO 20022 structured payment data helps finance teams build cleaner treasury controls across payment initiation, vendor master data, bank statements, investigations, reconciliation, and audit evidence.
IFRS 18 gives finance teams a cleaner ERP performance-data control layer.
How IFRS 18 helps finance teams build cleaner profit-and-loss presentation, management-defined performance measure governance, comparatives, XBRL tagging, and audit evidence through ERP data-control design.
ASU 2025-06 is not an accounting memo. It is an ERP software-cost control.
How FASB ASU 2025-06 turns internal-use software capitalization into ERP project-accounting, time-capture, procurement, amortization, impairment, transition, and audit-evidence design work.
Nacha 2026 is not a bank-only rule. It is an ERP payment-control deadline.
How Nacha 2026 ACH fraud-monitoring rules turn vendor bank changes, payroll account updates, payment runs, third-party sender oversight, and treasury evidence into ERP design work.
ViDA e-invoicing is not a format change. It is an ERP tax control system.
How EU ViDA, France 2026 e-invoicing, and Germany B2B mandates turn AR, AP, tax reporting, master data, and audit evidence into a real-time ERP control design problem.
FASB DISE is not a footnote project. It is an ERP expense data project.
How ASU 2024-03 turns expense disaggregation into an ERP design problem across close, payroll allocations, cost accounting, selling expense policy, and audit evidence.
Duplicate-Payment Prevention Across Channels (UI + API + Sync)
Duplicate-Payment Prevention Across Channels (UI + API + Sync) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Missing or Stale FX Rate Fallback and Quarantine
Missing or Stale FX Rate Fallback and Quarantine for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Multi-Currency Rounding Residual Distribution (Banker's Rounding)
Multi-Currency Rounding Residual Distribution (Banker's Rounding) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Backdated Transaction into a Reopened Prior Period
Backdated Transaction into a Reopened Prior Period for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Partial Failure Mid-Posting: Atomic Rollback / Saga Compensation
Partial Failure Mid-Posting: Atomic Rollback / Saga Compensation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Idempotent Retry of a Duplicated Create (external_id Anchor)
Idempotent Retry of a Duplicated Create (external_id Anchor) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Region- and Clearance-Scoped PII Masking in Consolidated Audits
Region- and Clearance-Scoped PII Masking in Consolidated Audits for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Concurrent Balance-Update Race Prevention
Concurrent Balance-Update Race Prevention for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Mid-Period Tax Rate Change with Version-Controlled Rate Tables
Mid-Period Tax Rate Change with Version-Controlled Rate Tables for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Break-Glass Emergency Authorization Bypass with Mandatory Audit
Break-Glass Emergency Authorization Bypass with Mandatory Audit for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Tax Determination by Tax Point Date, Not Entry Date
Tax Determination by Tax Point Date, Not Entry Date for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Master Data Management - Chart of Accounts Governance
Master Data Management - Chart of Accounts Governance for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Cross-Currency Triangulated Payment (Three-Leg FX)
Cross-Currency Triangulated Payment (Three-Leg FX) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Bank Feed Integration via Open Banking / Plaid / Direct Bank API
Bank Feed Integration via Open Banking / Plaid / Direct Bank API for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Approval Workflow Engine with Delegation and Escalation
Approval Workflow Engine with Delegation and Escalation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Data Import via CSV / XLSX with Validation and Error Reporting
Data Import via CSV / XLSX with Validation and Error Reporting for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Open REST API with OAuth 2.0 Client Credentials for Third-Party Integration
Open REST API with OAuth 2.0 Client Credentials for Third-Party Integration for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Webhook Event Delivery with Retry and Signature Verification
Webhook Event Delivery with Retry and Signature Verification for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Multi-Factor Authentication Policy Enforcement
Multi-Factor Authentication Policy Enforcement for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Immutable Audit Log and Compliance Trail
Immutable Audit Log and Compliance Trail for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
SCIM 2.0 Automated User Provisioning and Deprovisioning
SCIM 2.0 Automated User Provisioning and Deprovisioning for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Multi-Entity / Multi-Tenant Hierarchy Administration
Multi-Entity / Multi-Tenant Hierarchy Administration for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
SSO / SAML 2.0 and OIDC Identity Provider Integration
SSO / SAML 2.0 and OIDC Identity Provider Integration for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Asset Impairment Testing and Write-Down
Asset Impairment Testing and Write-Down for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Role-Based Access Control with Segregation of Duties Enforcement
Role-Based Access Control with Segregation of Duties Enforcement for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Asset Transfer Between Entities or Cost Centers
Asset Transfer Between Entities or Cost Centers for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Physical Asset Inventory Audit with Barcode/RFID Scanning
Physical Asset Inventory Audit with Barcode/RFID Scanning for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Partial Asset Disposal with Remaining Asset Continuation
Partial Asset Disposal with Remaining Asset Continuation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Construction-in-Progress (CIP) Tracking and Capitalization
Construction-in-Progress (CIP) Tracking and Capitalization for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Multiple Depreciation Books (Book vs Tax)
Multiple Depreciation Books (Book vs Tax) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Asset Disposal - Full Retirement with Gain/Loss Calculation
Asset Disposal - Full Retirement with Gain/Loss Calculation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Operating Lease Accounting under ASC 842
Operating Lease Accounting under ASC 842 for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Lease Modification and Remeasurement
Lease Modification and Remeasurement for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Depreciation Run and GL Posting (Straight-Line)
Depreciation Run and GL Posting (Straight-Line) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Finance Lease Recognition under ASC 842 / IFRS 16
Finance Lease Recognition under ASC 842 / IFRS 16 for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Asset Capitalization from Vendor Invoice
Asset Capitalization from Vendor Invoice for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Work-in-Progress (WIP) Tracking, Aging, and Write-Off
Work-in-Progress (WIP) Tracking, Aging, and Write-Off for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Project Profitability and Margin Analysis
Project Profitability and Margin Analysis for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Project Expense Capture, Approval, and Billable Reimbursement
Project Expense Capture, Approval, and Billable Reimbursement for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Subscription and Usage-Based Revenue Recognition
Subscription and Usage-Based Revenue Recognition for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Contract Modification Handling (Scope Change, Price Change, Termination)
Contract Modification Handling (Scope Change, Price Change, Termination) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Resource Planning, Capacity Management, and Utilization Tracking
Resource Planning, Capacity Management, and Utilization Tracking for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Deferred Revenue Schedule Automation and Amortization
Deferred Revenue Schedule Automation and Amortization for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Percentage-of-Completion (POC) Revenue Recognition for Fixed-Fee Projects
Percentage-of-Completion (POC) Revenue Recognition for Fixed-Fee Projects for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Milestone-Based Billing and Revenue Recognition
Milestone-Based Billing and Revenue Recognition for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Time and Material (T&M) Project Billing with Approved Timesheet Integration
Time and Material (T&M) Project Billing with Approved Timesheet Integration for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
ASC 606 / IFRS 15 Performance Obligation Identification and SSP Allocation
ASC 606 / IFRS 15 Performance Obligation Identification and SSP Allocation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Project Setup with Work Breakdown Structure (WBS) and Budget Baseline
Project Setup with Work Breakdown Structure (WBS) and Budget Baseline for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Labor Cost Allocation to Projects & Cost Centers
Labor Cost Allocation to Projects & Cost Centers for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Recruiting & Applicant Tracking (ATS)
Recruiting & Applicant Tracking (ATS) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Off-Cycle Payroll Run (Correction / Bonus)
Off-Cycle Payroll Run (Correction / Bonus) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Payroll GL Posting & Accruals
Payroll GL Posting & Accruals for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Payroll Reconciliation & Variance Analysis
Payroll Reconciliation & Variance Analysis for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Time & Attendance Tracking and Approval
Time & Attendance Tracking and Approval for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Leave / PTO Request, Approval & Accrual Management
Leave / PTO Request, Approval & Accrual Management for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Benefits Administration & Open Enrollment
Benefits Administration & Open Enrollment for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Employee Offboarding & Final Pay Calculation
Employee Offboarding & Final Pay Calculation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Tax Withholding Calculation & W-2 / T4 Filing
Tax Withholding Calculation & W-2 / T4 Filing for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Run Regular Payroll (Gross-to-Net Calculation)
Run Regular Payroll (Gross-to-Net Calculation) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Employee Onboarding - New Hire Setup
Employee Onboarding - New Hire Setup for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Contract Renewal Management
Contract Renewal Management for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Territory and Quota Management
Territory and Quota Management for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Contract Creation and E-Signature
Contract Creation and E-Signature for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Customer 360 View
Customer 360 View for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Sales Commission Calculation and Payout
Sales Commission Calculation and Payout for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Customer Master Record Creation and Deduplication
Customer Master Record Creation and Deduplication for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Sales Order Entry and Confirmation
Sales Order Entry and Confirmation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Pricing and Discount Management
Pricing and Discount Management for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Sales Forecasting and Commit Management
Sales Forecasting and Commit Management for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Configure-Price-Quote (CPQ) Generation
Configure-Price-Quote (CPQ) Generation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Opportunity Creation and Pipeline Progression
Opportunity Creation and Pipeline Progression for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Freight Bill Audit and Carrier Invoice Reconciliation
Freight Bill Audit and Carrier Invoice Reconciliation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Lead Capture and Qualification
Lead Capture and Qualification for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Shipping Label Generation and Carrier Manifesting
Shipping Label Generation and Carrier Manifesting for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Shipment Tracking and Delivery Event Monitoring
Shipment Tracking and Delivery Event Monitoring for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Carrier Rate Shopping and Carrier Selection at Shipment Creation
Carrier Rate Shopping and Carrier Selection at Shipment Creation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Distribution Requirements Planning (DRP) and Replenishment from DC to Branch
Distribution Requirements Planning (DRP) and Replenishment from DC to Branch for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Capable-to-Promise (CTP) Check for Make-to-Order Products
Capable-to-Promise (CTP) Check for Make-to-Order Products for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Material Requirements Planning (MRP) Run and Purchase Requisition Generation
Material Requirements Planning (MRP) Run and Purchase Requisition Generation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Supplier Lead-Time Management and Dynamic Safety Stock Recalculation
Supplier Lead-Time Management and Dynamic Safety Stock Recalculation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Master Production Schedule (MPS) Generation and Firm-Zone Management
Master Production Schedule (MPS) Generation and Firm-Zone Management for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Sales & Operations Planning (S&OP) Consensus Cycle
Sales & Operations Planning (S&OP) Consensus Cycle for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Available-to-Promise (ATP) Real-Time Check at Order Entry
Available-to-Promise (ATP) Real-Time Check at Order Entry for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Subcontracting / Outside Processing Purchase Order
Subcontracting / Outside Processing Purchase Order for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Statistical Demand Forecast Generation
Statistical Demand Forecast Generation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Scrap & Rework Management
Scrap & Rework Management for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Engineering Change Order (ECO) Management
Engineering Change Order (ECO) Management for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Work-In-Process (WIP) Valuation & Period-End Close
Work-In-Process (WIP) Valuation & Period-End Close for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Component Backflushing at Work Order Completion
Component Backflushing at Work Order Completion for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Capacity Planning & Finite Scheduling
Capacity Planning & Finite Scheduling for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Shop Floor Data Collection via Barcode / Terminal
Shop Floor Data Collection via Barcode / Terminal for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Work Order / Production Order Release & Dispatch
Work Order / Production Order Release & Dispatch for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Production Costing: Standard Cost Roll-Up
Production Costing: Standard Cost Roll-Up for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Master Production Schedule (MPS) Creation & Approval
Master Production Schedule (MPS) Creation & Approval for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Material Requirements Planning (MRP) Run & Action Message Processing
Material Requirements Planning (MRP) Run & Action Message Processing for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Multi-Level Bill of Materials Creation & Versioning
Multi-Level Bill of Materials Creation & Versioning for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Inter-Warehouse / Inter-Location Stock Transfer
Inter-Warehouse / Inter-Location Stock Transfer for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Lot / Batch Tracking Through the Supply Chain
Lot / Batch Tracking Through the Supply Chain for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Annual Physical Inventory (Wall-to-Wall Count)
Annual Physical Inventory (Wall-to-Wall Count) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Inventory Adjustment and Write-Off
Inventory Adjustment and Write-Off for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Cycle Count Scheduling and Execution
Cycle Count Scheduling and Execution for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Standard Cost Setup and Purchase Price Variance Capture
Standard Cost Setup and Purchase Price Variance Capture for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Sales Order Pick, Pack, and Ship
Sales Order Pick, Pack, and Ship for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Weighted-Average Cost Recalculation on Receipt
Weighted-Average Cost Recalculation on Receipt for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Item / SKU Master Creation and Maintenance
Item / SKU Master Creation and Maintenance for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Inventory Valuation via FIFO Costing
Inventory Valuation via FIFO Costing for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Goods Receipt Against Purchase Order
Goods Receipt Against Purchase Order for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Directed Putaway to Bin Location
Directed Putaway to Bin Location for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Supplier Catalog and Guided Buying
Supplier Catalog and Guided Buying for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
PO Change Order (Amendment)
PO Change Order (Amendment) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Spend Analysis and Category Management Dashboard
Spend Analysis and Category Management Dashboard for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Contract PO Linked to Master Supply Agreement
Contract PO Linked to Master Supply Agreement for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Supplier Performance Scorecard and Rating
Supplier Performance Scorecard and Rating for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
RFQ (Request for Quotation) Sourcing Event
RFQ (Request for Quotation) Sourcing Event for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Blanket Purchase Order with Release Management
Blanket Purchase Order with Release Management for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Goods Receipt Note (GRN) Recording
Goods Receipt Note (GRN) Recording for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Three-Way Match: PO, Goods Receipt, and Vendor Invoice
Three-Way Match: PO, Goods Receipt, and Vendor Invoice for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Supplier Onboarding and Qualification
Supplier Onboarding and Qualification for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Purchase Requisition Submission and Approval Workflow
Purchase Requisition Submission and Approval Workflow for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
1042 / 1042-S Preparation and Filing for Foreign Persons
1042 / 1042-S Preparation and Filing for Foreign Persons for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Purchase Order Creation from Approved Requisition
Purchase Order Creation from Approved Requisition for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Withholding Tax Calculation and Remittance
Withholding Tax Calculation and Remittance for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
1099 Preparation, Review, and IRS Filing
1099 Preparation, Review, and IRS Filing for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Exemption Certificate Management and Validation
Exemption Certificate Management and Validation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
E-Invoicing Mandate Compliance (LATAM - Mexico CFDI, Brazil NF-e)
E-Invoicing Mandate Compliance (LATAM - Mexico CFDI, Brazil NF-e) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
SAF-T File Generation and Submission (Portugal / Poland / Norway)
SAF-T File Generation and Submission (Portugal / Poland / Norway) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
VAT Return Preparation and Submission (EU / UK)
VAT Return Preparation and Submission (EU / UK) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
GST Determination, Filing, and Remittance (India)
GST Determination, Filing, and Remittance (India) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Tax Remittance and Payment to Taxing Authorities
Tax Remittance and Payment to Taxing Authorities for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Nexus Tracking and Economic Nexus Threshold Monitoring
Nexus Tracking and Economic Nexus Threshold Monitoring for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Tax Return Preparation and Multi-Jurisdiction Filing
Tax Return Preparation and Multi-Jurisdiction Filing for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Reforecasting Mid-Year
Reforecasting Mid-Year for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Real-Time Sales Tax / VAT / GST Determination at Transaction Entry
Real-Time Sales Tax / VAT / GST Determination at Transaction Entry for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Top-Down and Bottom-Up Budget Reconciliation
Top-Down and Bottom-Up Budget Reconciliation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Budget Approval Workflow and Lock
Budget Approval Workflow and Lock for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
What-If and Sensitivity Analysis
What-If and Sensitivity Analysis for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Capital Expenditure (CapEx) Planning and Approval
Capital Expenditure (CapEx) Planning and Approval for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Budget Scenario Planning (Base, Upside, Downside)
Budget Scenario Planning (Base, Upside, Downside) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Headcount and Workforce Planning
Headcount and Workforce Planning for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Budget vs. Actual Variance Analysis
Budget vs. Actual Variance Analysis for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Driver-Based Revenue Planning
Driver-Based Revenue Planning for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Rolling 12-Month Forecast Update
Rolling 12-Month Forecast Update for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Department-Level Budget Submission and Review
Department-Level Budget Submission and Review for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Annual Operating Budget Build (Top-Down Initiation)
Annual Operating Budget Build (Top-Down Initiation) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Cash Flow Statement Generation (Indirect Method)
Cash Flow Statement Generation (Indirect Method) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Statement of Changes in Equity
Statement of Changes in Equity for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Consolidated Income Statement Generation
Consolidated Income Statement Generation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Consolidated Balance Sheet Generation
Consolidated Balance Sheet Generation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Flux and Variance Analysis with Commentary
Flux and Variance Analysis with Commentary for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Multi-Entity Consolidation with Currency Translation
Multi-Entity Consolidation with Currency Translation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Trial Balance Review and Analytical Drill-Down
Trial Balance Review and Analytical Drill-Down for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Account Reconciliation Workflow and Sign-Off
Account Reconciliation Workflow and Sign-Off for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Intercompany Transaction Matching and Elimination
Intercompany Transaction Matching and Elimination for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Month-End Accrual Journal Entry Creation and Reversal
Month-End Accrual Journal Entry Creation and Reversal for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Period-End Close Checklist Orchestration
Period-End Close Checklist Orchestration for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Soft Close vs. Hard Period Lock Controls
Soft Close vs. Hard Period Lock Controls for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Stop Payment Issuance and Tracking
Stop Payment Issuance and Tracking for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Intercompany Cash Transfer and Settlement
Intercompany Cash Transfer and Settlement for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Positive Pay File Submission and Exception Management
Positive Pay File Submission and Exception Management for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Cash Flow Forecasting - 13-Week Rolling Forecast
Cash Flow Forecasting - 13-Week Rolling Forecast for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Bank Account Master Data Management
Bank Account Master Data Management for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Outbound Payment File Generation - NACHA ACH
Outbound Payment File Generation - NACHA ACH for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
ISO 20022 / pain.001 Payment File Generation
ISO 20022 / pain.001 Payment File Generation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Bank Transfer Between Internal Accounts
Bank Transfer Between Internal Accounts for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Bank Reconciliation - Automated Transaction Matching
Bank Reconciliation - Automated Transaction Matching for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
BAI2 / MT940 Bank Statement File Import
BAI2 / MT940 Bank Statement File Import for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Daily Cash Position Consolidation Across All Bank Accounts
Daily Cash Position Consolidation Across All Bank Accounts for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Automated Bank Feed Connection via Plaid / Open Banking
Automated Bank Feed Connection via Plaid / Open Banking for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Write Off an Uncollectible Invoice as Bad Debt
Write Off an Uncollectible Invoice as Bad Debt for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Capture Payment via Online Payment Link / Gateway
Capture Payment via Online Payment Link / Gateway for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Handle Multi-Currency Invoice and FX Cash Application
Handle Multi-Currency Invoice and FX Cash Application for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Process a Customer Refund
Process a Customer Refund for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Recognize Deferred Revenue on a Prepaid Subscription Invoice
Recognize Deferred Revenue on a Prepaid Subscription Invoice for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Run Automated Dunning / Collections Workflow
Run Automated Dunning / Collections Workflow for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Generate and Distribute AR Aging Report
Generate and Distribute AR Aging Report for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Issue a Credit Memo Against a Posted Invoice
Issue a Credit Memo Against a Posted Invoice for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Manage Customer Master Record and Credit Limit
Manage Customer Master Record and Credit Limit for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Auto-Match Payments via Bank Lockbox Import
Auto-Match Payments via Bank Lockbox Import for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Apply a Customer Payment to an Open Invoice
Apply a Customer Payment to an Open Invoice for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Two-Way PO/Invoice Match (No Goods Receipt)
Two-Way PO/Invoice Match (No Goods Receipt) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Create and Send a One-Off Sales Invoice
Create and Send a One-Off Sales Invoice for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Vendor Refund Receipt (Cash Refund of Unapplied Credit Balance)
Vendor Refund Receipt (Cash Refund of Unapplied Credit Balance) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Accrual for Unbilled Received Goods (Receipt Accrual)
Accrual for Unbilled Received Goods (Receipt Accrual) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Vendor Credit Memo Application
Vendor Credit Memo Application for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Early-Payment Discount Capture
Early-Payment Discount Capture for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Accounts Payable Aging Report
Accounts Payable Aging Report for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Duplicate Invoice Detection and Prevention
Duplicate Invoice Detection and Prevention for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Payment Run Execution (ACH / Wire / Check)
Payment Run Execution (ACH / Wire / Check) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Invoice Approval Workflow with Delegation and Escalation
Invoice Approval Workflow with Delegation and Escalation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Vendor Onboarding and Master Data Setup
Vendor Onboarding and Master Data Setup for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Invoice Capture via OCR and Email Ingestion
Invoice Capture via OCR and Email Ingestion for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Opening Balance Import for New Entity
Opening Balance Import for New Entity for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Three-Way PO/Receipt/Invoice Match and Auto-Approval
Three-Way PO/Receipt/Invoice Match and Auto-Approval for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Intercompany Transaction Posting and Elimination
Intercompany Transaction Posting and Elimination for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Trial Balance Generation and Drill-Through
Trial Balance Generation and Drill-Through for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Sub-Ledger to GL Reconciliation (AP)
Sub-Ledger to GL Reconciliation (AP) for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Reversing Journal Entry
Reversing Journal Entry for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Accrual Entry with Automated Reversal
Accrual Entry with Automated Reversal for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Recurring Journal Entry Automation
Recurring Journal Entry Automation for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Multi-Currency Transaction Posting with FX Conversion
Multi-Currency Transaction Posting with FX Conversion for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Unrealized FX Gain/Loss Revaluation at Period End
Unrealized FX Gain/Loss Revaluation at Period End for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Period Close with Hard Lock
Period Close with Hard Lock for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Chart of Accounts Setup and Maintenance
Chart of Accounts Setup and Maintenance for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.
Accounts payable automation is not invoice capture. It is the ERP control layer.
How AP connects vendors, purchase orders, bills, approvals, payments, tax, close, audit evidence, and cash forecasting.
Post a Manual Journal Entry with Double-Entry Enforcement
Post a Manual Journal Entry with Double-Entry Enforcement for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.