Business DSO Test
What the Business DSO Test Is and when teams use it
Why a standardized Business DSO Test matters
A consistent Business DSO Test reduces reporting errors, speeds month-end close, and improves cash-forecast accuracy. It creates an auditable trail of invoice-level evidence and documented exceptions to support financial controls and lender covenant reporting.
Who typically completes and reviews the Business DSO Test
Finance, credit, and audit teams use this template to standardize DSO calculations and document exceptions before distributing results to leadership.
- Accounts Receivable teams prepare invoice lists and aging reconciliations for each customer and period.
- Finance controllers and FP&A review aggregated DSO metrics and reconcile to the general ledger.
- Internal and external auditors use the test to sample invoices, confirm payments, and evaluate controls.
The same completed file is also used by external auditors, treasury teams, and lenders to validate receivables, cash forecasts, and covenant compliance.
Key roles who sign or approve the test
AR Manager
The Accounts Receivable Manager compiles invoice and payment data, documents disputed items, and certifies the accuracy of the aging schedule for each reporting period.
Finance Controller
The Finance Controller reviews reconciliations, approves the final DSO figure, and signs any attestations required for internal reporting or external lender covenants.
Risks and consequences of an incorrect Business DSO Test
Common preparation errors to avoid
- Including unapplied cash or credit memos without clear linkage to invoices, which inflates or deflates outstanding balances and skews DSO.
- Using inconsistent date conventions across lines (e.g., invoice date vs. service date) that create duplicate aging buckets and reconciliation mismatches.
- Failing to record disputed items or credit notes in a dedicated exceptions section, making it difficult for reviewers to assess collectible balances.
- Manual copy-paste between systems without validation, increasing data-entry errors and making audit trails incomplete.
Step-by-step: complete the Business DSO Test
-
01Prepare source data: Export invoices, payments, and credit memos from the AR ledger.
-
02Populate template: Enter invoice-level data into the standardized fields.
-
03Reconcile totals: Match AR ledger balances to the worksheet totals.
-
04Approve and archive: Controller approval and store final file with evidence.
Configuring the online Business DSO Test workflow
| Field | Configuration |
|---|---|
| Authentication | Email + optional SMS or SSO |
| Conditional Fields | Show exception fields when balance flagged |
| Auto-calculation | Formulas compute days outstanding automatically |
| Storage Format | PDF/A archived with audit trail |
Where to send the completed Business DSO Test
-
Submit to AR team: Primary preparer uploads completed sheet and supporting files.
-
Route for approval: Controller or finance lead reviews and signs electronically.
-
Archive evidence: Store final PDF with audit trail in records repository.
-
Share reports: Distribute summarized DSO figures to FP&A and treasury.
Digital signing and platform considerations
Choose a platform that supports secure e-signatures, audit trails, and integration with your document repository and ERP.
- Integrations: Salesforce, NetSuite, Microsoft 365, Google Workspace
- File types: PDF, Word DOCX, Excel
- Authentication: Email, SMS code, SSO options
Comparing eSignature vendor pricing and basic capabilities
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial, no credit card | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Available on Business Premium and above | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA required) | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
Practical tips for accurate, efficient Business DSO Tests
Typical timelines and internal deadlines for DSO reporting
Reporting Period Close:
Cut off AR activity at period end; include post-period receipts in notes.
Template Submission:
AR team submits completed test within 3 business days after close.
Manager Review:
Controller reviews and signs within 5 business days after submission.
Audit Sampling Window:
Provide sample documentation to auditors within agreed audit timelines.
Archive:
Move final signed file to secure records repository after approval.
Real-world examples of electronic testing and signatures
Optica Ventures LLC
Optica consolidated invoicing across portfolios for month-end DSO testing.
- Standard templates ensured consistent entries across teams.
- The team reported faster preparation and simpler customer follow-ups while preserving an auditable history for each period.
Tech Data
Tech Data modernized document routing for receivables and approvals.
- Centralized signing reduced delays in internal approvals.
- The company cited improved internal service and quicker revenue recognition workflows supported by secure audit trails.
Frequently asked questions about the Business DSO Test
-
Can the Business DSO Test be e-signed?
Yes. Electronic signatures that meet ESIGN (15 U.S.C. §7001) and applicable state UETA rules are generally enforceable if you document signer intent, consent, attribution, and retention capability.
-
What if DSO totals do not match the GL?
Reconcile line items by invoice number and date. Investigate unapplied cash, timing differences, and credit memos; document each reconciling item in the exceptions log.
-
Are notarization or witnesses required?
Typically not for internal financial worksheets. If formal attestations are necessary, check state RON/notary rules and preserve any required notarized acknowledgements.
-
How long must I keep completed tests?
Follow federal minima (IRS 3 years, IRC §6501(a)) and industry rules; healthcare records require six years under 45 CFR §164.530(j). Adjust for state or contractual requirements.
-
Which authentication level should we use?
Use at least email verification for routine approvals; employ stronger methods (SMS, SSO, KBA) when governance or external attestations require higher assurance.
-
What evidence should accompany the signed file?
Include source extracts (AR ledger), remittance advices, exception notes, signer name/title, timestamp, and the platform audit trail showing IP, timestamp, and actions.