Apportix by Synthronix
Request a review

Reporting · FDS & Allocation Support

The report gets filed either way. The method is what gets questioned.

Every year, the allocation and FDS reporting package goes out the door. The question an auditor asks isn't whether it exists — it's whether your agency can explain, defend, and reproduce every number in it. Apportix makes the reporting defensible by making the methodology agency-owned: traceable from GL/TB exports, through the allocation, to FDS backup, with review and approval preserved.

Request a review See how the review works

Boundary, up front: Apportix supports FDS reporting and produces draft journal-entry output for review. It does not submit to HUD/REAC, post journal entries, or replace your GL. Your finance team approves the method.

Provenance · Explain This Number

Pick a line on the FDS report. Trace it all the way back.

This is the test the reporting package has to pass. One allocated amount should show its ancestry — from source GL activity, through the cost pool and basis, to the FDS line it supports, with the reviewer and locked run version attached. Here is what that trace looks like for the highlighted line above.

  1. Source GL activityGL/TB export · FYE

    Benefit expense as recorded in your general ledger, brought in as a GL/TB export. Apportix reads the export; it never writes to your ledger.

    GL account6120 · Employee Benefits
    Period total412,800.00
  2. Cost poolPOOL-ADMIN-BEN

    The expense lands in a defined pool — Administrative Employee Benefits — with a documented scope of what belongs in it and what doesn't.

    Pool total412,800.00
  3. Allocation basisBASIS · Direct salaries

    The pool allocates on direct administrative salaries by program. The basis choice carries a written rationale, not just a formula.

    RationaleBenefits follow payroll
  4. Basis valueSupport attached

    The salary figures behind the basis are stored with the model — the support an auditor asks for is already attached to the number that used it.

    HCV direct salaries1,027,400.00
    All programs2,880,900.00
  5. Share percentageComputed in run

    The percentage is computed inside the locked run — reproducible from the same inputs, not retyped between tabs.

    HCV share35.66%
  6. Recipient programHCV

    The allocated amount posts to the Housing Choice Voucher program within the model, alongside every other program's share of the same pool.

    Allocated to HCV147,212.00
  7. FDS supportLine 91500 backup

    The amount maps to FDS line 91500 with a support schedule showing pool, basis, computation, and source — the backup behind the reported figure.

  8. Draft journal-entry outputFor review · Not posted

    Apportix produces draft JE output for your finance team to review and enter through your own GL process. Nothing is posted by the software.

  9. Reviewer & locked runApproval history preserved

    The methodology was reviewed and approved by finance before the run was locked. The reviewer, the decision, and the run version stay with the number.

    Run statusApproved · Locked

Lineage

From GL/TB, through the model, to the reporting package.

The trace above works because the whole path is structured. Inputs stay evidence. The model stays reviewable. Outputs stay reproducible.

InputsWhat exists today
  • GL/TB exportsTrial balance and detail from your existing GL/ERP
  • Prior allocation workbookThe starting point, not the destination
  • Basis inputsSalaries, units, square footage, headcount — with support files
  • Supporting documentationAttached where it's used, not in a shared-drive folder
ModelAgency-owned
  • Cost poolsDefined scope, documented contents
  • Allocation basesEach with a written rationale
  • Program & project dimensionsMapped to your FDS structure
  • Review decisionsWho approved what, and when
OutputsThe reporting package
  • Allocation runLocked, versioned, reproducible
  • FDS backupLine-level support schedules
  • ReconciliationAllocated totals tie back to the GL/TB
  • Draft journal-entry outputPrepared for review — never posted

Apportix works around your GL, not in place of it. The general ledger stays the system of record; Apportix is the home for the methodology that turns GL activity into a defensible allocation and FDS reporting package.

Methodology Ledger

The method itself, written down and reviewable.

Not a formula buried in a cell. Each pool carries its basis, its rationale, its support status, and its owner — the record an auditor can actually read.

Illustrative methodology ledger: cost pools with their allocation bases, rationale, support status, and owner.
Ref Cost pool Allocation basis Rationale Support Owner Status
P-01 Executive & Governance Total operating expense by program Leadership effort scales with overall program activity. Supported Finance Director Approved
P-02 Admin Employee Benefits Direct admin salaries by program Benefits follow payroll; salary support attached. Supported Finance Director Approved
P-03 Facilities — Central Office Occupied square footage Space-driven costs allocate on measured space. Supported Fee Accountant Approved
P-04 IT & Systems Headcount by program Per-seat cost driver; headcount roster attached. Supported Finance Director In review
P-05 Insurance — General Units under management Exposure scales with portfolio size. Pending Fee Accountant In review
Illustrative structure — your pools, bases, and rationale come from your agency's actual method. Every row: who owns it, what supports it, who approved it.

Review & Approval

Finance approves the method. Then the run locks.

The software structures candidates and drafts. It does not decide. Nothing reaches the reporting package without your finance team's review, and the decision itself becomes part of the record.

01 Candidate surfaced

Apportix structures a candidate methodology from your GL/TB exports, prior workbook, and basis inputs.

Actor: Apportix (draft only)
02 Finance review

Your finance team reads the pools, bases, and rationale — the same ledger shown above.

Actor: Finance
03 Edits requested

Changes go back with notes. The revision history stays with the model, not in an email thread.

Actor: Finance
04 Approved

A named reviewer approves the method. The approval — reviewer, decision, timestamp — is preserved.

Actor: Finance / Management
05 Run locked

The allocation run executes against the approved method and locks. The version is reproducible from its inputs.

Output: locked run + approval history
◈ Approved & Locked Reviewer · decision · timestamp · run version — preserved with the package, carried into next year's cycle.

Ownership

Where does the method live right now?

Most agencies can produce the report. Fewer can produce the reasoning. The difference is whether the methodology is borrowed or owned.

Today, at most agencies

Outside-owned

  • A consultant's workbookThe formulas work — for whoever built them.
  • An inherited spreadsheetMaintained by the person who left two FYs ago.
  • Rationale in staff memory"That's how we've always done it" is not a support schedule.
  • Support scattered across foldersFindable in March. Not in fieldwork.
  • Approval by email, if at allNo record of who signed off on the method.

A borrowed explanation.

With Apportix

Agency-owned

  • A documented methodology modelPools, bases, and rationale written down, in one place.
  • GL-led schedulesEvery run starts from your GL/TB exports and ties back to them.
  • Review decisions preservedWho approved the method, when, and what changed.
  • FDS backup attached to the numbersLine-level support, generated from the locked run.
  • The model carries forwardNext year starts from this year's approved, preserved model.

An owned explanation.

Year-End Deliverables

What actually comes out at year-end.

Not screenshots. A packet your finance team, fee accountant, and auditor can work from — every artifact traceable to the locked run that produced it.

Reporting support package Generated from the approved, locked run
  1. 01
    allocation-run — locked & versionedThe full allocation: pools, bases, computations, and program-level results, reproducible from its inputs.
    Run record
  2. 02
    fds-backup — line-level support schedulesFor each supported FDS line: the amount, the pool and basis behind it, and the computation that produced it.
    Schedules
  3. 03
    gl-tb-reconciliationAllocated totals tied back to the source GL/TB exports. Nothing in the package floats free of the ledger.
    Reconciliation
  4. 04
    draft-je-output — for reviewDraft journal-entry output prepared for your finance team to review and enter through your own GL process. Not posted by Apportix.
    Draft · Review
  5. 05
    support-package-exportBasis support and attached documentation, exported with the run so fieldwork requests don't start a folder hunt.
    Export
  6. 06
    review-approval-historyWho reviewed, what was requested, who approved, and when — the decision record behind the method.
    History
  7. 07
    preserved-methodology-modelThe approved model, carried forward. Next year's cycle starts from an owned method, not a blank workbook.
    Model

Boundaries

What Apportix is — and is not.

Finance buyers need constraints as much as capabilities. These are the lines, stated plainly.

A home for allocation methodologyPools, bases, rationale, and support — structured and reviewable.
Not a GL or ERP replacementYour general ledger stays the system of record. Apportix works around it.
Built around GL/TB exportsReads your exports; every run reconciles back to them.
Does not write to your ledgerDraft journal-entry output is prepared for review, never posted.
FDS backup supportLine-level support schedules generated from the locked run.
Does not submit to HUD/REACYour agency submits through the official process. Apportix supports the backup behind it.
A structured review workflowCandidates surfaced, edits tracked, approvals preserved.
Does not approve the methodFinance and management approve. The software structures; people decide.
A preserved, agency-owned modelThe approved method carries into the next cycle, owned by your agency.
Not an auditorOutside experts can still review everything. The black box is the problem — not the review.

Allocation Methodology Review

Could you defend this year's package line by line?

Start with an Allocation Methodology Review. We look at how your current method is documented, where the support lives, and what it would take for the reporting package to trace cleanly from GL/TB to FDS backup — before the next cycle, not during fieldwork.

Request a review See how the review works

Reviews are scoped to your agency's programs, GL/TB export quality, and existing method. No public pricing page — scope drives the conversation. Data is handled with tenant isolation, role-based access, and controlled exports; security documentation is available on request.