The tables behind Architecture Firm Management

Use stable source IDs when importing references. Team members.User resolves the signed-in user; accounting documents.Owner refers to team members. Match owner filters through that identity relationship. Project is text on design billing milestones, so agree a consistent naming convention. Drawing revision identifies the drawing issue used for the fee.

Review decisions.Parent references accounting documents and source revision identifies the reviewed document revision. Design billing milestones has its own Revision and decision at. Keep milestone acceptance evidence attached to the parent document and name the milestone and drawing issue clearly.

Cash receipts inherits organization context through Partner. Cash applications must connect a receipt and document with compatible partner and organization scope. Operation key identifies an operation; expected revision identifies the document version requested. Preserve external reference and effect references when reconciling an outcome.

Money fields use USD. Organizations.Currency records the organization setting; agree any external conversion before comparing monetary values.

1. Load Organizations and Users, resolving the Users.User reference, then team members with their User and Organization references.
2. Load business partners and ledger accounts within the appropriate Organization, then accounting periods.
3. Load accounting documents with Organization, Owner and Counterparty references; add design billing milestones and document lines against their Parent.
4. Load record attachments, review decisions and operation receipts with source revisions and actor references intact.
5. Load journal entries with Document and Period, then journal lines with Journal and Account. Reconcile historical posting states separately from new work.
6. Load cash receipts with Partner, then cash applications with Receipt and Document. Compare receipt totals and active applications before opening the next cycle.