Reference
Finance Policy Approval Record
Approval packet for activating an AMS accounting policy without implying statutory compliance.
First created Last updated
AMS ships a complete, certified non-production management reference policy so a workspace never has to begin with an empty form. It populates all twelve decision areas and includes worked owned-asset, loaned-custody, and maintenance examples. The reference is deliberately incapable of production activation: an accountable finance approver must clone, adapt, review, and sign the selected policy before it can become effective.
Download the reference policy JSON and its JSON Schema, or open AMS → Finance → Reference policy. The certificate command is pnpm workspace-assets:certify:policy.
Decision packet
Attach or reference:
- legal entity and books covered;
- applicable PFRS, IFRS, tax, management, donor, lender, or other reporting basis;
- functional and presentation currencies plus exchange-rate sources;
- fiscal calendar and open/soft-close/hard-close rules;
- capitalization and materiality thresholds;
- asset classes, significant-component rules, useful-life ranges, residual-value policy, methods, and conventions;
- inventory classification and approved specific-identification, FIFO, or weighted-average formula;
- impairment indicators, review cadence, evidence, reversal limits, and revaluation policy if enabled;
- account, cost-centre, project, funding, tax, and journal-export mappings;
- approval thresholds, maker-checker roles, recent-AAL2 actions, retention, and audit-pack requirements;
- transition treatment for opening balances and the first effective period;
- test results for allocations, currency, depreciation, components, impairment, NRV, inventory layers, disposal, close, reversal, and external receipt reconciliation.
Required decisions
The values below are worked samples, not silent defaults. A production candidate must record each replacement or explicit adoption. “System default” is not an acceptable accounting conclusion.
| Decision | Certified reference sample | Production action |
|---|---|---|
| Reporting basis and version | Management-only operational subledger; no statutory filing claim | Select applicable basis and version |
| Functional/presentation currency | PHP; retain source currency and approved rate lineage | Approve currencies and rate source |
| Capitalization/materiality thresholds | Illustrative PHP 25,000 per item; low-value controlled items remain operationally tracked | Replace or explicitly adopt from materiality evidence |
| Asset classes and useful lives | IT 3 years; audiovisual, furniture, and logistics equipment 5 years; significant components separate | Validate by expected consumption and evidence |
| Residual values and review cadence | Zero unless market evidence supports another value; annual estimate review | Approve class rules and review owner |
| Permitted depreciation methods/conventions | Straight-line/daily default; usage method only with reliable meter | Approve methods per class |
| Inventory cost formula by class | Specific identification for serialized; weighted average for interchangeable bulk; no LIFO | Approve class mapping |
| Impairment/revaluation policy | Trigger and annual indicator review; cost model; revaluation disabled | Approve indicators, evidence, and reversal rules |
| Fiscal calendar and close authority | Calendar year, monthly periods, five-business-day soft close, finance-approver hard close | Confirm calendar and delegated authority |
| Account and cost-centre mappings | Illustrative 1600/1690/6100/6150/5100 accounts; partner cost centres required | Replace with approved chart mappings |
| Approval and step-up thresholds | Different proposer/approver; recent AAL2 for activation and sensitive postings | Approve thresholds and role assignments |
| Effective date and transition method | No sample effective date; prospective activation after opening-balance reconciliation | Set date only on approved candidate |
Approval statement
The approver should record:
- approver name and accountable role;
- professional qualification or delegated authority, where required;
- decision: approve, approve with conditions, or reject;
- policy version and immutable payload/hash reviewed;
- effective date and first fiscal period;
- conditions, exceptions, review date, and superseded version;
- server timestamp and authenticated approval receipt.
The proposer and approver must be different people. Activation must use the signed-in approver identity; a typed name in notes is not sufficient. Rejection or conditional approval keeps the candidate policy inactive. A later policy version applies prospectively and cannot rewrite a closed period.
Certification boundary
AMS certifies the completeness and immutability of the reference package, rejects its production activation, and certifies deterministic calculations, immutable posting, maker-checker separation, hard period locks, balanced journal export/receipt reconciliation, and explicit basis/currency/policy lineage. The software-delivery gate is therefore complete. Production activation remains a deployment decision and does not imply that Furries PH selected the correct PFRS, IFRS, tax, or statutory treatment.
Use IAS 16, IAS 2, IAS 36, and applicable Philippine requirements as source material, with professional advice where needed. These references do not make AMS a general ledger, filing product, or compliance opinion.