FinOps Center
Month Close & Accrual

Most companies pay their AWS bill before the business has approved any of it.

The invoice arrives. Finance pays it because AWS must be paid. The business sign-off, if it happens at all, happens after the money is gone. FinOps Center inverts that order — approval happens before the accrual is finalized, so the company pays against numbers the business already owns.

WHY DID WE BUILD?

The accrual is the moment Finance books the AWS cost. If the business has not approved it yet, Finance is booking a number nobody owns.

The governance loop closes when approval precedes the accrual.

The two-gate workflow in Spend Governance feeds Month Close. By the time the billing period ends, every spend card has been reviewed and accepted by the Portfolio Owner. Every estimate-size gate has been signed off. FinOps Center confirms org-wide approval completeness before the accrual is exported. The FinOps Lead sees which owners have not yet completed their spend review and routes the outstanding approvals before closing.

The approved financial data is then exported in whatever delimited or file format the customer's system of record requires — AP, FP&A, or ERP. The company posts that file to its close process. This is how most accrual integration actually works: period-batched and file-based. FinOps Center claims the governance loop and the approved-data output. It does not claim live ERP connectors.

THE GOVERNANCE LOOP

One loop. From the approved budget to the paid bill.

Approved annual budgetimported by fileScheduledmonthly plan by workloadSpentactuals tracked at estimate grainApprovedtwo gates, Portfolio OwnerApproved accrualexported by fileAWS bill paidagainst approved numbers

Every step in the loop is a business decision, recorded against the hierarchy. The loop closes when the paid bill matches numbers the business already approved.

WHAT FINOPS CENTER PROVIDES AT CLOSE

Three close capabilities. All owned by the FinOps Lead.

01

Approve before the bill is owned

Month-end confirmation that all spend across the organization has been approved by the businesses who own it. The FinOps Lead sees approval completeness across every portfolio, department, and business unit. Outstanding approvals are surfaced and routed before the accrual is exported. The accrual is not finalized until the approval is complete.

02

Export approved accrual data by file

FinOps Center produces business-approved accrual data in any delimited or file format the customer's system of record requires. CSV, Excel, fixed-width, or custom delimiter — the export matches what the AP, FP&A, or ERP system expects. The company posts that file to its close process. Period-batched and file-based, which is how most accrual integration actually works.

03

Close the loop

Approved financial data is attributable at every rollup level — product, portfolio, department, business unit. Reconciliation is complete. All spend is allocated and owned before the invoice is paid. The month-end conversation starts with shared numbers the business signed off, not a bill Finance is explaining for the first time.

WHAT WE DO NOT CLAIM

FinOps Center exports approved accrual data. It does not provide live connectors to SAP, Coupa, Workday, or any other ERP system. Integration with those systems is a separate product decision. The export is file-based because that is how most enterprise close processes actually receive accrual data — period-batched, validated, and posted by the finance team.

Close the month against numbers the business already owns.

support@finopscenter.com