Link each record to its document without guessing
Finding the same number does not establish universal identity or document authenticity. Define scope, keys and checks before linking information. Think² organises collaborators with context, groups, an optional computer per collaborator, compatible models and authorised tools. This local example does not establish an integration or a matching process executed in Think².
Waitlist: no guaranteed immediate access or free plan. The destination is in Spanish.
Situations to review
One candidate matches the defined identifiers
Search within the same tenant and issuer, compare client and invoice reference, and check amount and currency separately. One consistent candidate can proceed to review under the business rule.
You retain a proposed relationship with explicit fields and sources, rather than inferring it from a name or amount. Matching fields does not prove document authenticity.
Identifiers match but the amount conflicts
Keep the identifier-based candidate and expose the amount or currency discrepancy. This fictional rule does not allow that match to become a validated link.
The conflict remains visible for an authorised person to resolve. Do not change a figure to force a match or declare that the document is false.
A key is missing or several candidates appear
Exclude documents with incomplete keys from automatic candidate searches. If several consistent candidates exist, retain them and mark the result ambiguous rather than choosing the latest arrival.
Do not infer a missing client from similarity or assume that two documents are the same retry. Cardinality, duplicates and idempotency require separate rules.
Waitlist: no guaranteed immediate access or free plan. The destination is in Spanish.
How to evaluate the work
- Define scope, keys and the permitted relationship. Every object in this fixture has tenant Tdemo and issuer Edemo. The exact keys are tenant, issuer, client and invoice. In a real system an invoice identifier may repeat across issuers; do not cross organisations based on similarity. Define business-specific cardinality rather than imposing a universal one-to-one relationship. Decision matrix: use exact keys within a defined scope to propose candidates; add amount and currency checks to expose discrepancies, not replace identity; retain an incomplete or ambiguous outcome when keys are missing or candidates multiply. If the business allows several documents per record, define that cardinality first rather than forcing one-to-one links to obtain a clean result.
- Check key completeness and search for exact matches. The local test compared strings in fictional objects only. Amount and currency are consistency checks, not sufficient identifiers. For real amounts, define types, precision, rounding and permitted tolerances; comparing the strings 100 and 100.00 does not normalise numbers.
- Apply an explicit rule and preserve evidence. Local rule: documents with missing keys are incomplete; for each record, any candidate with a conflicting amount or currency produces conflicto; otherwise multiple candidates produce ambiguo, one produces candidata_unica and none produces sin_candidata. These Spanish state labels are retained from the local script. This priority is not universally appropriate. Reviewing candidates does not authorise external changes: specific approval is required.
Reusable template: cutoff/scope; record/version; keys; document/source/version; fields compared; differences; candidates; rule/cardinality; state; review; external action/approval; verified result. Fictional example: every object has tenant Tdemo and issuer Edemo. N01 client C1, invoice F001, amount 100 USD; N02 client C2, invoice F002, amount 200 USD.
First snapshot: D01 C1/F001/100 USD; D02 C2/F002/250 USD; D03 missing client/F001/100 USD. A local deterministic script returned N01 candidata_unica with D01, N02 conflicto with D02 because 200 differs from 250, and D03 incomplete and excluded. The second snapshot adds D04 C1/F001/100 USD: N01 becomes ambiguo with D01 and D04; N02 remains in conflict and D03 incomplete.
Local assertions checked those outputs using fictional objects. No AI, real documents, integration or Think² execution was involved. Each D is a distinct fixture entry: whether D01/D04 were duplicates or retries was not evaluated. No accuracy, savings or authenticity was established.
Frequently asked questions
Does an exact invoice match prove that a document is correct?
No. It only establishes that the fields and scope compared in that test match. Truth, current validity, authorisation and document validity need separate checks.
Can a name, amount or the latest document resolve the match?
Not under this example's rule. A missing client remains incomplete; two consistent candidates remain ambiguous. Do not invent a confidence percentage or replace a missing key with similarity.
Must the relationship always be one to one?
No. Cardinality is business-specific. Define it alongside rules for partial documents, versions, differences and source identifiers. This teaching rule does not grant access or authorise external writes.
Sources and scope
- W3C — PROV-O — Entities, activities, agents and provenance relations; not invoice keys, matching rules or proof of truth/authority.
Keep exploring
- Prepare accounts-payable review (Spanish)
- Control access and company data (Spanish)
- An optional computer per collaborator (Spanish)
- Approve external actions (Spanish)
Waitlist: no guaranteed immediate access or free plan. The destination is in Spanish.