Skip to main content

S_00002 — One operating record with the ledger synchronized

kind: solution_catalog
schema_version: 1
solutions:
- id: S_00002
proofIds: []
priority: 70
name: 'One operating record with the ledger synchronized'
status: approved
mechanism: >-
Hold quotes, orders, production, material consumption, and shipments in one
operating record, and synchronize the general ledger to it rather than
keeping two parallel versions of the same activity. Margin by site and by
unit is then read from the operating record instead of being reassembled by
hand, and the costing unit and the selling unit are carried on the item so
the conversion is applied consistently rather than remembered.
capabilities:
- name: 'Quote-to-cash, inventory, and manufacturing on one operating record'
classification: native
conditions:
- 'Per-unit margin depends on consumption and hours being captured at production time.'
- 'The record is only as granular as the data entered into it.'
evidence_ids: []
- name: 'General ledger synchronization with QuickBooks'
classification: integrated
conditions:
- 'Requires a QuickBooks account.'
- 'The ledger stays in QuickBooks. This is synchronization, not replacement.'
evidence_ids: []
- name: 'Costing and business intelligence views over the operating record'
classification: native
conditions:
- 'Views reflect what the operating record captures and no more.'
evidence_ids: []
- name: 'Item-level custom properties carrying costing unit, selling unit, and conversion'
classification: configured
conditions:
- 'The customer states the conversion for each product.'
- 'A conversion that varies by product has to be defined per product.'
evidence_ids: []
- name: 'Finance-specific dashboards and charts'
classification: configured
conditions:
- >-
Built with the customer. The call was ambiguous on whether a self-serve
builder exists, so this is recorded at the lower classification.
evidence_ids: []
- name: 'Native financial module and year-end close'
classification: roadmap
conditions:
- 'Seller stated it is "in the works" and gave no release date.'
- 'Until it ships, year-end close stays in QuickBooks.'
- 'Must not be presented as available.'
evidence_ids: []
expected_outcome_hypotheses:
- 'Margin can be read per site and per unit from one record rather than rebuilt per question.'
- 'A volume or spread scenario question can be answered without manual assembly.'
- 'Scrap and leftover material can be attributed to the job or line that produced them.'
- 'The costing-to-selling unit conversion is applied consistently rather than by memory.'
limitations:
- 'Financial close is not native today. It remains in the accounting package.'
- >-
Per-unit margin is only as good as the consumption and labour capture at
production. Where those are not recorded, the gap moves rather than closes.
- 'Multi-currency quoting was raised on the call and never answered. Treat it as an open requirement, not a capability.'
- 'Historic margin is not reconstructed. The record starts when the data starts.'
prohibited_claims:
- 'That a native financial module or year-end close is available.'
- 'That the general ledger moves off the incumbent accounting package.'
- 'Any quantified saving, recovered margin, close-time reduction, or accuracy figure.'
- 'That multi-currency or multi-unit quoting is supported. That is unverified.'
- 'That the customer''s existing reported financials are wrong.'