Make sure the prices really conflict
Compare the service, unit, currency, billing period and customer scope. A monthly support fee and a one-time setup charge can look inconsistent even though they cover different work. Record the precise item and value from each source.
Keep the original files intact. Record their names, locations and relevant rows instead of silently renaming one ‘final’ or replacing its contents.
Find the approval and its effective date
A modification date shows when a file changed. Look for the owner, an approval that identifies the item or version, and the date the decision takes effect. If a message is ambiguous, confirm what it refers to.
An authorized owner can mark a version current for a defined scope, mark an earlier version superseded or leave the conflict unresolved. If authority or evidence is missing, hold the affected quote.
- List every competing version for the same item and scope.
- Record the owner, effective date and approval evidence.
- Ask the authorized owner to document the resolution.
A fictional monthly support price
The fictional register shows PL-01 at USD 1,200 and PL-02 at USD 1,350. The owner approved PL-02 to replace PL-01 for new quotes from June 15. A newer file, PL-03 at USD 1,290, has no approval reference and remains unverified.
The newest filename is therefore not the deciding factor in this example. All prices, dates, names and approvals are fictional, and the complete comparison remains in the original worksheet.
Make the decision easy to apply
Record the version, affected services and customers, effective date and decision maker. Clarify what happens to quotes already prepared under an earlier figure. Retain the replaced version with its status so past work remains understandable.
Put the current reference where quote preparers can find it and identify old copies in folders or proposal templates. This process resolves a reference conflict; setting the price is a separate decision.
Prepare the comparison with Areinum
Areinum Assistant can help put the supplied price rows, dates and approval references side by side and identify gaps. The authorized owner still determines which price applies.
See the example
Price list version comparison register
The business, owner names, prices, approval notes, file names, and dates are fictional.
| Item | Version | Price | Currency | Effective date | Source reference | Owner | Approval evidence | Status | Resolution |
|---|---|---|---|---|---|---|---|---|---|
| Monthly support package | PL-01 | 1200 | USD | 2026-04-01 | Fictional file: rates-april.csv | Maya Chen | Fictional owner approval dated 2026-03-28 | Superseded | Replaced by PL-02 from 2026-06-15 |
| Monthly support package | PL-02 | 1350 | USD | 2026-06-15 | Fictional file: rates-june.csv | Maya Chen | Fictional approval note naming PL-02 | Current in example | Owner confirmed this version for new quotes |
| Monthly support package | PL-03 | 1290 | USD | 2026-07-01 | Fictional attachment: rates-final-v3.csv | Unknown | No approval reference found | Unverified | Do not quote until the authorized owner decides |
- Enter one row for each version of the same item, keeping units, currency, and customer scope visible.
- Link to the source file or approval record and write the effective date rather than relying on a file's modified date.
- Let an authorized owner set the resolution. Keep unapproved versions visible as unverified until resolved.
- The names, values, dates, and files are fictional.
Limits of this method
- The selected research class is H. This exact price conflict use case is a proposal supported by an adjacent ownership and verification mechanism, not measured demand.
- A date or file modification time does not establish approval authority. The business must identify its own decision maker.
- The cited Notion features concern Notion pages and plans. They do not establish that Areinum verifies prices or tracks versions.
Questions you may have
Should we use the newest attachment?
Only after checking the item, scope, effective date and approval. A modification date alone is not an approval.
What if the documents use different billing periods?
Record those differences before comparing amounts. A monthly fee and a one-time fee may not conflict at all.
Can an old price list be deleted after a decision?
Retain the historical record according to your business's practices and label it superseded so it is not mistaken for the current reference.
Sources and further reading
- Wikis & verified pages
Notion describes page ownership, verification status and reminders. The price comparison is a separate manual process.
A verification feature does not establish which price is approved, and availability depends on the applicable plan.
Notion documents page owners, verification status, time-limited or indefinite verification, and notifications when verification expires.
This is documentation for Notion knowledge pages. It does not document price list reconciliation or prove that verification establishes the correct price. Some individual-page and database verification cases have plan requirements stated on the page.
2026-10-18
The demo is in English. Access may need to be arranged.
Explore the demo