Evaluate Xero inventory by separating the item catalogue, tracked quantities and accounting value. Test one representative item through a physical-count difference and inspect the resulting records before accepting an adjustment workflow. A reusable invoice item is useful, but it should not be treated as proof that inventory tracking and accounting configuration are complete.
Begin with the exact question your team needs answered: can it explain what is held, what changed and how the change is valued? The original reconciliation card below keeps these questions together while giving each its own evidence. It is suitable for a discussion between a stock owner, an accounts owner and the person responsible for an integration.
Is a saved item the same as tracked inventory?
Xero describes reusing saved item details on quotes, invoices and purchase orders. Its South African inventory product page presents this as a way to avoid repeatedly typing item information. That is a catalogue convenience. When preparing a demonstration, ask whether each example is merely a reusable line item or is configured for tracked inventory.
The Xero Item schema identifies tracked inventory through inventory asset and cost-of-goods-sold account codes. The schema requires the inventory asset account to have type INVENTORY. These conditions appear in the published Item schema. Have the accounts owner confirm the intended account mapping rather than accepting a product name or a tick box as sufficient evidence.
For a proposed integration, retain the item code, item identifier and relevant account mapping in a restricted configuration record. Ask the implementer to explain how an incoming catalogue record is matched with its existing counterpart. A changed display name should not become an accidental instruction to create a second item.
Keep the initial example small. Choose an item that the stock owner can recognise physically and that the accounts owner can explain financially. Once the team agrees how that record behaves, add other item types and exceptions. A large import is a poor way to discover that two teams mean different things by “tracked”.
What do quantity and value fields actually describe?
Xero defines TotalCostPool as the value on hand calculated using average cost accounting. This is an accounting-value field in the Item schema, so label it separately from unit counts on the reconciliation card. Do not compare a financial value directly with a shelf quantity or treat a quantity match as a value reconciliation.
The schema states that QuantityOnHand is zero when QuantityOnBackOrder is greater than zero. The schema defines QuantityAvailable as QuantityOnHand minus QuantityOnBackOrder. Read those fields together rather than letting an integration display an unexplained number labelled simply “stock”. Ask which documented field feeds each report or screen being proposed.
The schema alone does not specify every business action that changes these figures. When an implementer proposes an adjustment, request the documented operation, its permissions and the evidence returned by the configured system. Keep reading a field separate from authority to change it. This gives the technical review a concrete target without guessing API write behaviour.
For broader movement terminology, see inventory control and its audit trail. Use that general framework to define what your business needs to explain, then map the requirement to Xero’s actual records.
| Question | Evidence to examine | Who should explain it? |
|---|---|---|
| Is this a reusable catalogue item? | Saved item details on a test transaction | Sales or accounts user |
| Is this tracked inventory? | Tracking state and required account mapping | Accounts owner |
| What is physically held? | Dated count sheet with item identity and unit | Stock owner |
| What quantity does the integration show? | Exact source field and related quantity states | Integration owner |
| How is the holding valued? | Value field and the corresponding accounting explanation | Accounts owner |
| Why was it changed? | Adjustment reason, approval and resulting references | Named reviewer |
How should a stock adjustment be reviewed?
Xero describes adjusting quantity, average cost and total value after a stocktake or damage. The product page establishes those adjustment concepts; use an authorised demonstration to learn the exact procedure and resulting records for the proposed account. Agree who can prepare a change and who must review it before testing.
A count difference needs an explanation before it needs a button. Check whether the item, counting unit and cut-off agree. Ask whether a recorded receipt, sale or previous correction accounts for the difference. If the cause remains unknown, preserve that uncertainty in the internal investigation instead of selecting a convenient reason to make the totals match.
Separate the quantity decision from the valuation decision. A stock controller may establish that goods are damaged, while the accounts owner decides how that event should be reflected financially. Request an explanation of the proposed posting and retain its reference with the physical evidence. The software demonstration should make that relationship inspectable.
Also ask what happens if the wrong item is selected. Request a correction or recovery demonstration using approved test data, and record the resulting references. Avoid testing a reversal on live books merely to see what the interface permits. The review should finish with a repeatable process and a named owner for unresolved accounting questions.
Original item reconciliation card: damaged stock
Consider this hypothetical example. A test record shows twelve units of a finished item. A physical count finds eleven units, including one damaged unit that the business wants assessed separately. The team must first agree what the eleven-unit count includes and what quantity should remain available under its approved process. The numbers are illustrative counts, not operating results.
Identify the record. Write the item code, counting unit, tracking state and test transaction references. Add the inventory asset and cost-of-goods-sold mapping for review. State the count’s cut-off and note any activity intentionally excluded from the exercise. The objective is a shared definition of the opening position.
Explain the difference. Keep separate lines for the missing physical unit and the damaged unit. Ask the stock owner to explain the evidence for each. Do not collapse them into a single unexplained reduction: one concerns a count discrepancy, while the other concerns the condition and intended treatment of an item that was found.
Capture the proposed change. Record the requested quantity treatment, the accounts owner’s valuation decision and the person authorised to approve the adjustment. Leave an unresolved decision open. Then have the demonstrator show the supported process in the test account and retain the resulting record references.
Compare the result. Read the relevant quantity fields together and inspect the value separately. Compare them with the agreed expectation, then ask another person to explain why the result follows from the inputs. If the explanation depends on an undocumented integration assumption, assign that assumption for investigation before rollout.
Close the card. Retain the original count, the cause established, the approval and the observed result. Mark quantity, valuation and correction handling individually as demonstrated or unresolved. This is more useful than a single overall tick beside “inventory works”.
What should an import or integration preserve?
Xero describes importing item details from CSV and exporting item lists. Treat an export as useful comparison evidence, and rehearse an import with a bounded test file. Agree which fields are expected to change and compare the resulting records with the starting copy before expanding the scope.
Setting IsSold to false nulls Description and SalesDetails in the Item schema. Setting IsPurchased to false nulls PurchaseDescription and PurchaseDetails in the Item schema. These documented side effects make status-field changes worth reviewing explicitly. Ask the integration owner to show how the relevant details are handled when those flags change.
Use Xero’s current product and account information to establish the proposed subscription and regional scope. For the wider implementation brief, see business systems. To discuss requirements, get started with the item reconciliation card and the decisions that still need an owner.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.