Case study · Finance and accounting

Month end close support for B2B SaaS

Company-reported case study

Actigy BPO supplied a six-person reconciliation and reporting team for Northwind Analytics. The company-reported case compares an 11-business-day close with a six-business-day close over four months; the SaaS controller retained sign-off.

Actigy BPO confirms the engagement and supporting records. Results apply to the stated scope and measurement windows.

Close cycle

Result

6 business days

Baseline: 11 business days

Window: 4 months

Supporting record: ERP report

Reconciliation accuracy

Result

99.9%

Baseline: 96.4%

Window: 4 months

Supporting record: ERP report

Manual journal entries

Result

38 / month

Baseline: 140 / month

Window: 4 months

Supporting record: ERP report

Client profile

Northwind Analytics, a US B2B SaaS company with 280 staff.

Challenge and scope

The controller relies on 14 spreadsheets, resolves about three reconciliation errors a month, and works weekends to close the books.

Month-end work stalls when the controller has to reconstruct which source report a spreadsheet used and which adjustments have already been reviewed. Different settlement dates can open differences across cash, clearing, and revenue schedules. Those differences need owners before the controller can sign off on the consolidated close.

Delivery workflow

Reconcile 4,200 monthly transactions across 28 balance sheet accounts and six revenue streams. Work through Stripe settlement differences, prepare journal entries for review, and organize schedules against the controller’s close calendar.

Reconcile Stripe payouts to bank activity and NetSuite entries using settlement IDs, transaction dates, fees, and refunds. Carry timing items forward with an expected clearing date. For gaps that require an adjustment, attach the supporting detail and the proposed journal to the appropriate account schedule.

Maintain a close calendar with a responsible preparer, reviewer, and cutoff for each account. Use one open-items list for unresolved reconciliations and late inputs. Deliver a close pack with account schedules, exception notes, and proposed entries so the controller can review material items in a single pass.

Delivery team

Poland, about 6 FTE. 1 finance delivery lead, 3 reconciliation specialists and 2 reporting associates.

Systems and tools

NetSuite, Stripe.

Client decision rights

The controller owns accounting policy and revenue recognition decisions and signs off on the close.

Early milestone

At week 6, the close takes eight business days in this case.

Outcomes

Company-reported results, with the baseline, measurement window and supporting record described for each measure.

Reported results: Month end close support for B2B SaaS
MeasureBaselineResultWindowSupporting record
Close cycle11 business days6 business days4 monthsERP report
Reconciliation accuracy96.4%99.9%4 monthsERP report
Manual journal entries140 / month38 / month4 monthsERP report

Interpreting the results

The five-business-day reduction in close time is useful alongside the rise in reconciliation accuracy. A reduction in manual journal entries can show that recurring sources are posting more consistently when adjusting entries and late changes are measured in both periods. Track the value and age of unresolved items at sign-off.

Recommendations for new clients

For SaaS teams with a close of 10 days or longer, start with one close cycle. Track business days from period end to controller sign-off and log adjustments made after sign-off.

Begin with a settlement account, a revenue-related account, and a balance sheet account with recurring timing items. Share the close calendar, prior schedules, and the controller’s review thresholds. Ask the team to produce schedules that the controller can reperform from the source report and trace every material adjustment before adding more entities or accounts.

Scope this workflow for your operation

Use the documented workflow, client-held decisions and operational checks to outline a pilot for your own workload.