Stored materials in a payment application: a practical tracking guide

What are stored materials in a payment application?

Imagine an electrical contractor receiving switchgear six weeks before the planned installation. The equipment belongs to a specific project, but it remains protected in a secure laydown area. The supplier invoice proves a purchase. The delivery ticket proves a delivery. Neither document, by itself, proves that the customer must recognize the value in this month’s payment application.

Assign every handoff to a named person. On the specialty contractor’s side:

• the procurement lead creates the batch and links the purchase order;
• the site receiver confirms identity, quantity, condition, location, and custody;
• the project manager confirms the contract line and signed scope;
• the billing coordinator maintains the register, reconciles the values, and assembles the required evidence;
• the internal reviewer checks the project rule, evidence, prior authoritative value, and current calculation;
• the authorized approver approves the exact version before external submission.

Outside that team, the supplier or fabricator provides the commercial and delivery records and may hold the material off-site. The general contractor or construction manager receives the request and assembles an upstream package when applicable. The customer or designated reviewer decides what amount the project procedure recognizes for the period. One person may perform more than one role, but the register should name the role used at each handoff.

When material is held away from the project site, record the warehouse operator or fabricator, the exact location, and who controls access. Do not replace those facts with the single status “off-site.”

Three boundaries prevent common errors:

1. Purchased is not installed. Procurement confirms an order or purchase, not field progress.
2. Delivered is not accepted. A physical receipt does not prove the reviewer’s decision.
3. Requested is not paid. Keep the requested, accepted or certified, invoiced, and paid amounts as separate states.

The term “stored materials” may appear as materials on hand, materials delivered but not incorporated, or another contract-specific label. Preserve the project’s term in the source record, then use one stable internal classification for reporting.

Start with the contract gate, not the supplier invoice

Before adding a batch to a payment application, answer the contract questions in writing. The answer may be a clause, supplementary condition, customer instruction, portal requirement, or formal decision. If the rule is unclear, the next action is to obtain a decision, not to invent a percentage.

Swipe horizontally to view all columns.

Treat conditions as fields, not as notes hidden in a PDF. For example, approved location: north secure laydown area is testable. Materials okay is not. If approval expires or depends on continued insurance, record the period and source.

Do not assume that the same rule applies to every material. Custom fabricated switchgear, standard conduit, rented equipment, and consumables can receive different treatment. One contract line may also separate material and labour values. Link the batch to the exact line and valuation basis used by the payment application.

Build a stored-material register that survives the next cycle

Create one row per identifiable batch, not one row per photograph or supplier invoice. A batch is the smallest group you can trace reliably through delivery, storage, partial installation, transfer, and final reconciliation. Give it an internal identifier such as MAT-014 and never recycle that identifier.

Download the ready-to-use register

Headers to copy into another system

Paste this tab-separated line into the first row of a spreadsheet:

Batch ID	Project	Contract line	Material description	Supplier	Purchase order	Supplier invoice	Quantity received	Unit	Received on	Current location	Eligibility source	Approved-location source	Location approval expiry	Custody holder	Condition checked on	Evidence index link	Submitted-revision history link	Decision history link	Movement and installation history link	Contract valuation basis	Required evidence rule	Amount basis	Tax treatment	Maximum eligible material value	Installed quantity to date	Quantity removed from eligible stock	Stored quantity at period end	Cumulative installed material value	Stored value at period end	Previously recognized cumulative value	Current-period material adjustment	Physical / work state	Evidence / eligibility state	Submission state	Current reviewer decision	Owner	Next action	Follow-up date

The row links four histories without merging or overwriting them:

• commercial source: purchase order, supplier invoice, and contract line;
• physical source: delivery ticket, quantity, location, condition, and photos;
• billing source: prior payment application, current request, and reviewer decision;
• action source: owner, next action, and confirmed follow-up date.

Keep the source files immutable. If a corrected supplier invoice arrives, add the new document and mark which record it replaces. If the batch moves, add a movement event with the time, from-location, to-location, quantity, person responsible, and proof. Update the current location only after preserving that event.

Keep quantity removed from eligible stock separate from installed and stored quantities. Back every removal with an exception event. If the treatment is confirmed, link the project’s contract decision. While that decision is pending, isolate the affected value, exclude it from eligible stored value, and assign a named owner and follow-up date. Calculate period-end stored quantity as quantity received minus quantity installed minus quantity removed from eligible stock. A “returned,” “damaged,” or “removed” label by itself must not leave those units in eligible stored value.

The three value fields are deliberately separate:

• cumulative installed material value is the eligible material portion incorporated into the work to date;
• stored value at period end is the eligible value that remains stored under the project rule;
• previously recognized cumulative value is the material value already included in accepted or otherwise authoritative prior billing totals under the project vocabulary.

Use the same amount basis and tax treatment for the maximum eligible value, installed value, stored value, and previously recognized value. If one amount includes tax, labour, holdback, or another adjustment that the others exclude, normalize the records before calculating.

Do not use a prior requested amount when the project’s authoritative prior value is a certified or accepted amount. Preserve both states elsewhere, then use the one the contract requires for this calculation.

Run the record from delivery through submission

1. Create the batch before the billing cut-off

The project manager or procurement lead creates the batch when material is ordered or when a delivery is expected. Link the purchase order and contract line. Record the expected location and the person responsible for custody. This gives billing time to resolve missing eligibility rules before month-end.

2. Verify the physical receipt

On receipt, a named person confirms the material description, count or measured quantity, condition, date, and location. Link photographs to the batch, not merely to the project folder. A useful photograph shows the material and enough surroundings to confirm the recorded location, but it does not replace a delivery record or inventory.

If only part of an order arrives, record the received quantity. Do not claim the full supplier invoice because the invoice covers a larger order. If several batches share one invoice, allocate the documentary link to each batch and preserve a clear allocation method.

3. Test the contract conditions

Billing checks each applicable condition from the contract gate. Keep four state fields separate because the same batch can be partly installed while its evidence is incomplete.

Physical or work state: expected, received or stored, partly installed, installed, or returned or disposed. This field describes what happened to the material.

Evidence or eligibility state: not assessed, evidence incomplete, ready for internal review, approved for this request, or removed or corrected. This field records the internal contract check for the current request.

Submission state: not submitted, submitted, or superseded. Link the state to the exact payment-application version.

Reviewer decision: pending, accepted or certified, partly accepted, or refused. Preserve the reviewer’s exact project term and link the decision to the submitted version. Never use the reviewer decision as the batch’s eligibility state.

4. Reconcile against the prior period

For each batch, start from the authoritative material value previously recognized. Add the current cumulative installed material value and current stored value, then calculate the difference. Investigate any negative or unexpectedly large result before submission.

When a prior request was only partly accepted, the request and decision remain separate. Do not silently use the larger value because it is more convenient. The payment-application tracker explains how to preserve those post-submission states.

5. Assemble the supporting documents by batch

Create a one-page batch index that lists the batch identifier, contract line, current quantity and location, requested adjustment, and links to required evidence. Keep the evidence package in the project’s required order. The index helps the reviewer navigate; it does not create eligibility.

6. Obtain internal approval of the exact version

The internal reviewer checks the contract rule, physical record, prior recognized value, current calculation, and evidence index. The authorized approver then approves the exact register, calculation, and supporting-file version before anything is sent outside the company. A later edit requires another approval.

7. Preserve the submitted revision and decision

Freeze the submitted register, calculation, and supporting file set. Record the date, recipient, channel, revision, and amount requested. Later, record the received decision separately. If the reviewer recognizes only part of a batch, preserve the affected quantity or value and the stated reason.

Worked example: move value without requesting it twice

Consider fictional batch MAT-014: 60 switchgear components allocated to one contract line. The simplified contract-assigned material value is $48,000 before tax, or $800 per component. Labour, holdback, tax, and other contract adjustments are excluded so the movement is visible. Assume the internal reviewer has confirmed that this material and location meet the project conditions.

Swipe horizontally to view all columns.

What MAT-014 looks like in the register

The complete row still holds its supplier, approval, owner, and follow-up fields. These key fields show how the same batch changes between the two cycles.

Swipe horizontally to view all columns.

In cycle 04, the customer’s designated reviewer accepts $48,000 as stored material. In cycle 05, 15 components move from storage into installed work. The installed material column increases by $12,000 while the stored column decreases by the same amount. The eligible cumulative value remains $48,000, so the current-period material adjustment is zero.

This is the anti-duplication control. The contractor reports the material’s new state, but does not request the same material value again. Cycle 06 completes the transfer with the same result.

If five components were damaged before installation and no longer eligible, the period-end eligible cumulative value would fall to $44,000. Compared with $48,000 previously recognized, the formula would produce −$4,000. Do not hide the negative result. Escalate it under the contract’s correction procedure and preserve the cause and decision.

Handle moves, partial deliveries, and refusals as events

Material moves to another location

Preserve a movement event before changing the current location. Recheck location approval, custody, protection, insurance evidence, and inventory. A move can change eligibility even if the batch and value do not change.

A supplier invoice covers several projects

Never attach the full value to each project. Split the material into traceable batches using received quantities and a documented allocation. Link every batch back to the same commercial source while keeping project totals mutually exclusive.

The reviewer recognizes only part of the request

Keep the full requested amount in the submitted revision. Record the recognized amount and reason as a separate decision. Update the next cycle from the prior authoritative value required by the project. Do not rewrite the old request to match the decision.

Material is returned, damaged, missing, or substituted

Add an event with quantity, date, source, and owner. Set affected value aside until the contract treatment is confirmed. A replacement receives its own traceable batch or an explicit relationship to the original. Photographs and informal messages do not authorize a valuation change.

Installation crosses the billing cut-off

Use the project’s stated cut-off and field record. Do not leave the same quantity in both stored and installed fields. If the state cannot be confirmed, assign a verification action rather than selecting the more favourable state.

Material is stored off-site

Record the full facility address, custodian, access control, segregation method, inventory date, and contract approval source. Seek qualified advice when ownership transfer, risk of loss, insurance, security interests, liens, or hypothecs matter. This guide does not resolve them.

What Quebec and Canadian public sources actually establish

The rules depend on the contract and project type. The following public sources illustrate useful record structures, but they do not create a universal right to claim stored materials.

For Quebec public construction contracts and public subcontracts covered by the prompt-payment framework, section 5 of the regulation requires the payment request to identify each claimed item, the associated period, and its value. Section 6 makes supporting documents depend on what the contract requires and what is essential to assess the request. Section 10 sets the refusal deadline for each actor; section 11 requires a written refusal to identify the refused amount, affected items, and reasons. The Quebec government guide explains that framework. Confirm that the framework covers the specific contract before relying on it.

For a private Quebec contract, article 2122 of the Civil Code of Québec permits an entrepreneur to demand instalments for work performed and materials necessary for the work when the agreement provides for them, after giving the client a statement of amounts paid and still owing to subcontractors, material suppliers, and other participants. It does not, by itself, supply this guide’s location, evidence, valuation, or anti-duplication rules. Read the actual agreement.

A federal tender provides a concrete anti-duplication example. Its GC5.4 payment clause addresses material delivered to the place of work but not yet incorporated, subject to contract compliance and the condition that it was not included in another progress report. That is a clause-specific illustration, not a standard that can be copied into every project. Public Services and Procurement Canada’s form 1792 also separates this-period values from total-to-date values, which supports cumulative reconciliation.

Finally, the Canada Revenue Agency’s real property GST/HST memorandum illustrates why a request for payment, a reviewer’s decision, an invoice, and a payment should not be collapsed into one status. Ask a tax adviser to determine the project’s actual GST/HST and QST treatment.

Stored-material payment application checklist

Frequently asked questions

Does a paid supplier invoice make stored material billable?

No universal rule does that. A paid invoice proves a commercial event. The contract and project procedure still determine eligibility, valuation, location, proof, and review.

Can off-site stored material be included?

Only when the applicable contract and project decision allow it and the required conditions are satisfied. Record the facility, custody, segregation, inventory, approval, and evidence. Obtain advice for ownership, insurance, lien, hypothec, or risk questions.

What is the most important anti-duplication control?

Keep one stable batch identifier and compare the current eligible cumulative value with the material value already recognized. When material moves from stored to installed, decrease stored value as installed value increases.

Should the supplier invoice value always be used?

No. Use the valuation basis defined for the project. The supplier invoice can be evidence without being the contract value used in the payment application.

What if the customer accepts less than requested?

Preserve the submitted request. Record the received decision, affected batch, recognized amount, reason, owner, and next action separately. Use the project’s required authoritative prior value in the next reconciliation.

Does “accepted” mean invoiced or paid?

No. Requested, accepted or certified, invoiced, and paid are separate records. Accounting remains authoritative for invoices and receipts.

Sources and next step

Sources were verified on September 3, 2026. The primary sources used for this guide are the Quebec prompt-payment regulation, the Quebec government explanatory guide, the Civil Code of Québec, the federal tender example, Public Services and Procurement Canada’s progress-payment form 1792, and the Canada Revenue Agency’s real property GST/HST memorandum. Verify the current text and the project’s coverage before acting.

The useful next step is small: choose one material batch expected in the next 30 days, assign a batch identifier, and complete the contract gate before the billing cut-off. That single row will reveal whether the team is missing a project rule, a physical record, a prior-period value, or an owner.

Keep the workbook. Automate the cycle when you are ready.

Use the workbook now. When the manual handoffs become the bottleneck, Aplon connects field progress, review, approval, submission proof, and collection follow-up.

A person still approves every external commitment.See how Aplon controls the cycle