AAIP record
Use current personal-data material for notice, purpose, rights, security, database-registration questions, and international transfers.
AUTHORITY-LOG / REVIEWED 2026-07-31
This log favors current first-party sources and records the product decision they inform. It does not convert a public page into a fact-specific legal, tax, payment, privacy, or commercial conclusion.
Use the closest authority, then confirm the operator-specific facts and provider documentation before implementation.
Use current personal-data material for notice, purpose, rights, security, database-registration questions, and international transfers.
Use the electronic-invoice portal for current systems and updates; the operator and advisers determine the actual taxpayer and document path.
Use Transferencias 3.0 material to understand official payment-system concepts, then use the selected provider's current technical contract.
Use regulator connectivity reporting to test performance assumptions; validate the target users, devices, and locations directly.
Record authority, title, URL, publication or update date, access date, language, relevant statement, and open questions.
Name the person who confirms applicability, the technical owner, and the business owner of the resulting behavior.
Tie the approved source interpretation to configuration, adapter version, fixture, content, release, and effective date.
Define the provider, policy, data, audience, document, transaction, authority, or scope change that triggers a recheck.
If the current authority or operator-specific answer is unknown, the system record should say unresolved rather than silently inherit an older assumption.