Accounting Data Mapping — Proposed Guide

Accounting Data Mapping: Mapping defines how a source expense representation becomes a target accounting record. It must account for entity, currency,…

Overview

Mapping defines how a source expense representation becomes a target accounting record. It must account for entity, currency, category and required dimensions.

Key concepts

Version the transformation and record unmatched values. Keep source ids separate from provider ids.

Implementation considerations

Do not silently choose a default account for an unknown category. A reviewable exception is safer than an unexplained posting.

Illustrative data model

This local fixture shows a possible representation for the concepts above. It is not an endpoint response, production configuration or a claim that the described capability is implemented.

{
  "reference_only": true,
  "topic": "Accounting Data Mapping",
  "mapping_version": 1,
  "category_id": "category_example_123",
  "account_id": "acct_example_123",
  "dimension_value_id": "dimension_value_example_123"
}

Design review checklist

• Document which organization owns the accounting data mapping representation and which actor may view or change it.
• Test the boundaries of mapping version, category id, account id, dimension value id using synthetic values, including missing or inconsistent references.
• Before future implementation, obtain an approved contract and review failure behavior. This documentation does not authorize production activation.

Proposed data types

Related documentation