DataBP POC
DataBP POC / Documents / Source profile

Entitlement and billing reconciliation: source profile

What the sources hold, column by column, and the data the app needs.

The reconciliation (DIG-655). Built from Pilot knowledge 111 item 813, version 51, as kept while building; private details such as addresses, identifiers and paths are masked here.

Branch Data Profiling

Profiling — Profile

Effort DIG-650, DataBP demo: the north-star Hex product; build DIG-654, branch rayserrano2735/dig-654-entitlement-and-billing in Integrationals/databp-dbt
Governed by Standard: Profiling (K#10 I#15)
Official copy method AGENTIC.DATASKILLS.KNOWLEDGE_ITEM_FROM_TEMPLATE
Template source K#10 I#186 — updated 2026-11-16 04:41 UTC — SHA-256 8ccdd1550b1a74bb327f52900bf63c160a79440383ef77bd167f1053471a0e6f
Status v1 — DRAFT — written 2026-11-19 16:27Z (compliance record not built; not presented for agreement)
Source system Three SQL Server databases on RDS databp-lab-sqlserver: the DataBP platform, the Salesforce extract, and usage reporting
Source location DATABP_SRC.dbo: client, customer, invoice (exist); product, entitlement, invoice_item (designed). DATABP_SFDC.dbo: Account, Product2, Opportunity, OpportunityLineItem, Contract (designed). DATABP_USAGE.dbo: usage_declaration (designed)
Profile date 2026-11-19
Profiler Claude, for Ray Serrano
Scope Every column the design document (knowledge 111 item 806) uses: the three existing tables measured from the data; the nine designed tables specified, with their rows and planted disagreements, their measured analyses NA until generated (created on Ray's answer 1y, 2026-11-19; the scope is the Profiling standard's, section 1 and section 3: a verdict for every column the design uses)
Population client 20, customer 5,000, invoice 20,008 rows (20,000 read 2026-11-18, design document R-1, and 8 added by phase one); designed tables, phase one, 2026-11-19: product 2, entitlement 12, invoice_item 8, Account 14, Product2 2, Contract 13, Opportunity 13, OpportunityLineItem 13, usage_declaration 12
Author Ray Serrano; edited by Claude
Classification Internal — Data Management

1. Quality standard

This profile follows Standard: Profiling (K#10 I#15): field intent, value discipline, and population for every column, and a verdict of Integrate, Defer, or Reject for each, naming its check. It does not redefine the criteria.

2. Data profile

Source ERD

Drawn first, before any column is profiled (section 6 of the standard): every source table in scope as it lands, in crow's-foot notation, with its real columns; a relationship solid only where a source declares it, otherwise dashed with its match rate counted in the data; an entity the sources imply but none sends drawn dashed. Stored as an svg block.

The source tables in scope, in three SQL Server databases, one per source system. The three that exist today, client, customer and invoice in DATABP_SRC.dbo, are drawn solid, with their real columns read from the information schema on 2026-11-19 at 16:29 UTC; each declares a primary key (PK) and none declares a foreign key. The nine designed tables are drawn dashed, with the columns the design sketch (knowledge 111 item 805, sections 8.2 to 8.4) gives them; they are not generated yet, and the sketch gives them no keys or types. Every relationship is dashed, since no foreign key is declared; the two among existing tables carry match rates counted at 16:30 UTC, and the designed ones are counted once the rows are generated. Joins between source systems are numbered and listed, not drawn. Two joins, 14 and 15, were missing from the design and were added on Ray's answers of 2026-11-19 (results P-1 and P-2, section 3). The database also holds sample100 (100 rows), a test table no design decision uses, and SQL Server's own MSchange_tracking_history; neither is in scope.

<svg width="100%" viewBox="0 0 680 1370" role="img" xmlns="http://www.w3.org/2000/svg" font-family="-apple-system, Segoe UI, Helvetica, Arial, sans-serif"><title>Source ERD: the three existing tables and the nine designed, by source system</title><desc>Three source systems as bands. DataBP platform (DATABP_SRC.dbo): client, customer and invoice exist; product, entitlement and invoice_item are designed. Salesforce extract (DATABP_SFDC.dbo): Account, Opportunity, OpportunityLineItem, Contract and Product2, designed. Usage reporting (DATABP_USAGE.dbo): usage_declaration, designed. Every relationship is dashed: no foreign key is declared. Joins between systems are numbered and listed; joins 14 and 15 were added after this profile found them missing.</desc><g fill="none" stroke="#c9c6bd" stroke-dasharray="6 4"><rect x="8" y="20" width="664" height="425" rx="12"/><rect x="8" y="455" width="664" height="380" rx="12"/><rect x="8" y="845" width="664" height="205" rx="12"/></g><g fill="#6b6963" font-size="13" font-weight="600"><text x="20" y="40">DataBP platform, DATABP_SRC.dbo</text><text x="20" y="475">Salesforce extract, DATABP_SFDC.dbo (designed)</text><text x="20" y="865">Usage reporting, DATABP_USAGE.dbo (designed)</text></g><g fill="#E1F5EE" stroke="#0F6E56"><rect x="20" y="50" width="140" height="66" rx="7"/><rect x="200" y="50" width="180" height="117" rx="7"/><rect x="420" y="50" width="240" height="151" rx="7"/></g><g fill="#F6FBF9" stroke="#0F6E56" stroke-dasharray="4 3"><rect x="20" y="250" width="140" height="134" rx="7"/><rect x="200" y="250" width="180" height="168" rx="7"/><rect x="420" y="250" width="240" height="168" rx="7"/><rect x="20" y="495" width="140" height="117" rx="7"/><rect x="200" y="495" width="180" height="134" rx="7"/><rect x="420" y="495" width="240" height="117" rx="7"/><rect x="20" y="665" width="140" height="151" rx="7"/><rect x="420" y="665" width="240" height="100" rx="7"/><rect x="200" y="885" width="260" height="151" rx="7"/></g><g fill="#085041" font-size="14" font-weight="600"><text x="30" y="70">client</text><text x="210" y="70">customer</text><text x="430" y="70">invoice</text><text x="30" y="270">product</text><text x="210" y="270">entitlement</text><text x="430" y="270">invoice_item</text><text x="30" y="515">Account</text><text x="210" y="515">Opportunity</text><text x="430" y="515">OpportunityLineItem</text><text x="30" y="685">Contract</text><text x="430" y="685">Product2</text><text x="210" y="905">usage_declaration</text></g><g fill="#0F6E56" font-size="11"><text x="105" y="70">20 rows</text><text x="315" y="70">5,000 rows</text><text x="590" y="70">20,000 rows</text><text x="105" y="270">designed</text><text x="325" y="270">designed</text><text x="605" y="270">designed</text><text x="105" y="515">designed</text><text x="325" y="515">designed</text><text x="605" y="515">designed</text><text x="105" y="685">designed</text><text x="605" y="685">designed</text><text x="405" y="905">designed</text></g><g stroke="#0F6E56" stroke-width="0.6"><line x1="20" y1="78" x2="160" y2="78"/><line x1="200" y1="78" x2="380" y2="78"/><line x1="420" y1="78" x2="660" y2="78"/><line x1="20" y1="278" x2="160" y2="278"/><line x1="200" y1="278" x2="380" y2="278"/><line x1="420" y1="278" x2="660" y2="278"/><line x1="20" y1="523" x2="160" y2="523"/><line x1="200" y1="523" x2="380" y2="523"/><line x1="420" y1="523" x2="660" y2="523"/><line x1="20" y1="693" x2="160" y2="693"/><line x1="420" y1="693" x2="660" y2="693"/><line x1="200" y1="913" x2="460" y2="913"/></g><g fill="#22211e" font-size="12"><text x="30" y="95">PK client_id</text><text x="30" y="112">client_name</text><text x="210" y="95">PK tenant_id</text><text x="210" y="112">PK customer_id</text><text x="210" y="129">customer_name</text><text x="210" y="146">email, nullable</text><text x="210" y="163">updated_at</text><text x="430" y="95">PK tenant_id</text><text x="430" y="112">PK invoice_id</text><text x="430" y="129">customer_id</text><text x="430" y="146">amount</text><text x="430" y="163">invoice_date</text><text x="430" y="180">status</text><text x="430" y="197">updated_at</text><text x="30" y="295">tenant_id</text><text x="30" y="312">product_id</text><text x="30" y="329">product_code</text><text x="30" y="346">product_name</text><text x="30" y="363">unit_price</text><text x="30" y="380">updated_at</text><text x="210" y="295">tenant_id</text><text x="210" y="312">entitlement_id</text><text x="210" y="329">customer_id</text><text x="210" y="346">product_id</text><text x="210" y="363">units</text><text x="210" y="380">start_date</text><text x="210" y="397">end_date</text><text x="210" y="414">updated_at</text><text x="430" y="295">tenant_id</text><text x="430" y="312">invoice_id</text><text x="430" y="329">item_id</text><text x="430" y="346">product_id</text><text x="430" y="363">units</text><text x="430" y="380">unit_price</text><text x="430" y="397">amount</text><text x="430" y="414">updated_at</text><text x="30" y="540">Id</text><text x="30" y="557">Name</text><text x="30" y="574">OwnerId</text><text x="30" y="591">Tenant__c</text><text x="30" y="608">Subscriber_Id__c</text><text x="210" y="540">Id</text><text x="210" y="557">AccountId</text><text x="210" y="574">ContractId</text><text x="210" y="591">StageName</text><text x="210" y="608">CloseDate</text><text x="210" y="625">Tenant__c</text><text x="430" y="540">Id</text><text x="430" y="557">OpportunityId</text><text x="430" y="574">Product2Id</text><text x="430" y="591">Quantity</text><text x="430" y="608">UnitPrice</text><text x="30" y="710">Id</text><text x="30" y="727">AccountId</text><text x="30" y="744">StartDate</text><text x="30" y="761">EndDate</text><text x="30" y="778">ContractTerm</text><text x="30" y="795">Status</text><text x="30" y="812">Tenant__c</text><text x="430" y="710">Id</text><text x="430" y="727">Name</text><text x="430" y="744">ProductCode</text><text x="430" y="761">Tenant__c</text><text x="210" y="930">tenant_id</text><text x="210" y="947">declaration_id</text><text x="210" y="964">customer_id</text><text x="210" y="981">product_code</text><text x="210" y="998">usage_month</text><text x="210" y="1015">declared_units</text><text x="210" y="1032">declared_at</text></g><g stroke="#6b6963" stroke-width="1.3" fill="none"><line x1="160" y1="88" x2="200" y2="88" stroke-dasharray="5 4"/><line x1="167" y1="81" x2="167" y2="95"/><line x1="188" y1="88" x2="200" y2="81"/><line x1="188" y1="88" x2="200" y2="95"/><line x1="380" y1="108" x2="420" y2="108" stroke-dasharray="5 4"/><line x1="387" y1="101" x2="387" y2="115"/><line x1="408" y1="108" x2="420" y2="101"/><line x1="408" y1="108" x2="420" y2="115"/><line x1="290" y1="167" x2="290" y2="250" stroke-dasharray="5 4"/><line x1="283" y1="174" x2="297" y2="174"/><line x1="290" y1="238" x2="283" y2="250"/><line x1="290" y1="238" x2="297" y2="250"/><line x1="160" y1="308" x2="200" y2="308" stroke-dasharray="5 4"/><line x1="167" y1="301" x2="167" y2="315"/><line x1="188" y1="308" x2="200" y2="301"/><line x1="188" y1="308" x2="200" y2="315"/><line x1="540" y1="201" x2="540" y2="250" stroke-dasharray="5 4"/><line x1="533" y1="208" x2="547" y2="208"/><line x1="540" y1="238" x2="533" y2="250"/><line x1="540" y1="238" x2="547" y2="250"/><path d="M 90 384 L 90 432 L 540 432 L 540 418" stroke-dasharray="5 4"/><line x1="83" y1="391" x2="97" y2="391"/><line x1="540" y1="430" x2="533" y2="418"/><line x1="540" y1="430" x2="547" y2="418"/><line x1="160" y1="550" x2="200" y2="550" stroke-dasharray="5 4"/><line x1="167" y1="543" x2="167" y2="557"/><line x1="188" y1="550" x2="200" y2="543"/><line x1="188" y1="550" x2="200" y2="557"/><line x1="380" y1="550" x2="420" y2="550" stroke-dasharray="5 4"/><line x1="387" y1="543" x2="387" y2="557"/><line x1="408" y1="550" x2="420" y2="543"/><line x1="408" y1="550" x2="420" y2="557"/><line x1="540" y1="665" x2="540" y2="612" stroke-dasharray="5 4"/><line x1="533" y1="658" x2="547" y2="658"/><line x1="540" y1="624" x2="533" y2="612"/><line x1="540" y1="624" x2="547" y2="612"/><line x1="90" y1="612" x2="90" y2="665" stroke-dasharray="5 4"/><line x1="83" y1="619" x2="97" y2="619"/><line x1="90" y1="653" x2="83" y2="665"/><line x1="90" y1="653" x2="97" y2="665"/><path d="M 290 629 L 290 740 L 160 740" stroke-dasharray="5 4"/><line x1="167" y1="733" x2="167" y2="747"/><line x1="290" y1="641" x2="283" y2="629"/><line x1="290" y1="641" x2="297" y2="629"/></g><g fill="#6b6963" font-size="12" font-weight="600"><text x="174" y="80">1</text><text x="394" y="100">2</text><text x="298" y="212">3</text><text x="174" y="300">4</text><text x="548" y="230">5</text><text x="300" y="446">6</text><text x="174" y="542">7</text><text x="394" y="542">8</text><text x="548" y="645">9</text><text x="98" y="645">10</text><text x="298" y="700">14</text></g><g fill="#22211e" font-size="12"><text x="20" y="1080" font-weight="600">Relationships. Dashed: no foreign key is declared. Bar: one; three prongs: many.</text><text x="20" y="1102">1  customer.tenant_id = client.client_id: 5,000 of 5,000 match (2026-11-19 16:30 UTC).</text><text x="20" y="1120">2  invoice (tenant_id, customer_id) = customer: 20,000 of 20,000 match (same read).</text><text x="20" y="1138">3  entitlement (tenant_id, customer_id) = customer. 4  entitlement (tenant_id, product_id) = product.</text><text x="20" y="1156">5  invoice_item (tenant_id, invoice_id) = invoice. 6  invoice_item (tenant_id, product_id) = product.</text><text x="20" y="1174">7  Opportunity.AccountId = Account.Id. 8  OpportunityLineItem.OpportunityId = Opportunity.Id.</text><text x="20" y="1192">9  OpportunityLineItem.Product2Id = Product2.Id. 10  Contract.AccountId = Account.Id.</text><text x="20" y="1210">Across systems, not drawn:</text><text x="20" y="1228">11  Account (Tenant__c, Subscriber_Id__c) = customer (tenant_id, customer_id).</text><text x="20" y="1246">12  usage_declaration (tenant_id, customer_id) = customer (tenant_id, customer_id).</text><text x="20" y="1264">13  usage_declaration (tenant_id, product_code) = Product2 (Tenant__c, ProductCode).</text><text x="20" y="1290" font-weight="600">Added on Ray's answers of 2026-11-19 (results P-1, P-2):</text><text x="20" y="1308">14  Opportunity.ContractId = Contract.Id, Salesforce's standard field.</text><text x="20" y="1326">15  Product2 (Tenant__c, ProductCode) = product (tenant_id, product_code).</text><text x="20" y="1352">Designed joins (3 to 15): every one matches all its rows in phase one (P-9).</text></g></svg>

2.0 Population context

Phase one of the product path (Profiling standard, section 1, two paths): the nine designed tables hold rows generated by the phase-one generator (tutorial, knowledge 111 item 463, step 26), one set per round-one path of P-6, all for one data provider, client 3, and one month, October 2026. There are no real subscribers, no test records mixed with real ones, and no history: every row was written in one transaction on 2026-11-19 between 18:44:43 and 18:45:15 UTC, and none has changed since. Base population for each table's percentages is its own row count. Measured where the pipeline reads them, the Snowflake copies the Openflow connector made in DATABP_LAB (schemas DATABP_SRC_DBO, DATABP_SFDC_DBO, DATABP_USAGE_DBO), on 2026-11-19 from 19:27 to 19:30 UTC; every table's count there equals SQL Server's (tutorial step 26, 19:24:28 UTC), and no row is marked deleted. Because the data was designed, a column that holds one value does so by the phase's scope (one data provider, one month, one contract term), not by a defect of the source; P-11 records it. The connector's own columns _SNOWFLAKE_INSERTED_AT, _SNOWFLAKE_UPDATED_AT and _SNOWFLAKE_DELETED are the pipeline's metadata, not source columns, and are not profiled here.

Sub-populations: none. Each designed table describes one entity for one data provider; no routing column splits any of them.

2.1 Tables

The nine designed tables come first (2.1.1 to 2.1.9), then the three existing tables, client, customer and invoice (2.1.10 to 2.1.12), whose keys and joins were read earlier (P-3 to P-5). For each: grain, then one row per column with populated count, distinct count, field intent, and the values or distribution. Histories (freshness, volume trend, change rate, disappearance): NA for phase one, one load and no change yet.

2.1.1 product (DATABP_SRC_DBO.PRODUCT), 2 rows

Grain: (tenant_id, product_id), 0 duplicates in 2 rows; (tenant_id, product_code) is also unique, 0 duplicates.

Column Populated Distinct Intent Values or distribution
tenant_id 2, 100% 1 Key, controlled 3 for both (P-11)
product_id 2, 100% 2 Key 1, 2
product_code 2, 100% 2 Controlled discrete, clean EQUITIES, OPTIONS
product_name 2, 100% 2 Label Equities feed, Options feed
unit_price 2, 100% 2 Numeric, dollars 40.00 and 50.00; mean 45.00, standard deviation 7.07; no zeros
updated_at 2, 100% 2 Timestamp 18:44:48.450 to 18:44:48.562 UTC, the load

2.1.2 entitlement (DATABP_SRC_DBO.ENTITLEMENT), 12 rows

Grain: (tenant_id, entitlement_id), 0 duplicates in 12 rows; (tenant_id, customer_id, product_id, start_date) is also unique, 0 duplicates.

Column Populated Distinct Intent Values or distribution
tenant_id 12, 100% 1 Key, controlled 3 (P-11)
entitlement_id 12, 100% 12 Key 1 to 14, two numbers unused (paths PA7 and PA11, no entitlement)
customer_id 12, 100% 12 Key 3 to 263; one subscriber per row
product_id 12, 100% 2 Key 2 seven times, 1 five times
units 12, 100% 3 Numeric count 10 six times, 12 four, 14 two; min 10, median 10, P75 12, P90 14, max 14; mean 11.33, standard deviation 1.56; no zeros
start_date 12, 100% 1 Date 2026-10-01 (P-11)
end_date 12, 100% 1 Date 2027-09-30 (P-11)
updated_at 12, 100% 12 Timestamp, near-unique 18:44:48.605 to 18:44:49.118 UTC, the load

2.1.3 invoice_item (DATABP_SRC_DBO.INVOICE_ITEM), 8 rows

Grain: (tenant_id, invoice_id, item_id), 0 duplicates in 8 rows.

Column Populated Distinct Intent Values or distribution
tenant_id 8, 100% 1 Key, controlled 3 (P-11)
invoice_id 8, 100% 8 Key 100001 to 100008, one item per invoice
item_id 8, 100% 1 Key 1 on every row: one item per invoice in phase one
product_id 8, 100% 2 Key 1 four times, 2 four times
units 8, 100% 2 Numeric count 10 seven times, 12 once (PA3, billed at reported units with no license); mean 10.25, standard deviation 0.71; no zeros
unit_price 8, 100% 2 Numeric, dollars 40.00 and 50.00, four each; equals the product's price on all 8 (join 6)
amount 8, 100% 3 Numeric, dollars 400.00 four times, 500.00 three, 600.00 once; equals units times unit_price on all 8
updated_at 8, 100% 8 Timestamp, near-unique 18:44:48.791 to 18:44:49.129 UTC, the load

The 8 invoices the items belong to were added to the existing invoice table: tenant 3, invoice_id 100001 to 100008, invoice_date 2026-10-31; 8 of 8 have an item.

2.1.4 Account (DATABP_SFDC_DBO.ACCOUNT), 14 rows

Grain: Id, 0 duplicates in 14 rows; (Tenant__c, Subscriber_Id__c) is also unique, 0 duplicates.

Column Populated Distinct Intent Values or distribution
Id 14, 100% 14 Key, 18 characters ACC0284581153E1152 to ACCFAC325B5EC7C816
Name 14, 100% 14 Label "Customer 3" to "Customer 263", the platform's customer name
OwnerId 14, 100% 1 Key USR57481771F2666E6 on all 14 (P-11)
Tenant__c 14, 100% 1 Key, controlled 3 (P-11)
Subscriber_Id__c 14, 100% 14 Key 3 to 263, step 20; one per path

2.1.5 Product2 (DATABP_SFDC_DBO.PRODUCT2), 2 rows

Grain: Id, 0 duplicates in 2 rows; (Tenant__c, ProductCode) is also unique, 0 duplicates.

Column Populated Distinct Intent Values or distribution
Id 2, 100% 2 Key PRD11F3581CE7E4DE8, PRDBBDD12FE8ABB57D
Name 2, 100% 2 Label Equities feed, Options feed; equal to product.product_name by code
ProductCode 2, 100% 2 Controlled discrete, clean EQUITIES, OPTIONS; equal to product.product_code (join 15)
Tenant__c 2, 100% 1 Key, controlled 3 (P-11)

2.1.6 Contract (DATABP_SFDC_DBO.CONTRACT), 13 rows

Grain: Id, 0 duplicates in 13 rows.

Column Populated Distinct Intent Values or distribution
Id 13, 100% 13 Key 18-character ids, prefix CTR
AccountId 13, 100% 13 Key one Contract per Account with a license
StartDate 13, 100% 1 Date 2026-10-01 (P-11)
EndDate 13, 100% 1 Date 2027-09-30 (P-11)
ContractTerm 13, 100% 1 Numeric, months 12 (P-11)
Status 13, 100% 1 Controlled discrete, clean Activated (P-11)
Tenant__c 13, 100% 1 Key, controlled 3 (P-11)

2.1.7 Opportunity (DATABP_SFDC_DBO.OPPORTUNITY), 13 rows

Grain: Id, 0 duplicates in 13 rows.

Column Populated Distinct Intent Values or distribution
Id 13, 100% 13 Key 18-character ids, prefix OPP
AccountId 13, 100% 13 Key one Opportunity per Account with a license
ContractId 13, 100% 13 Key one Opportunity per Contract (join 14)
StageName 13, 100% 1 Controlled discrete, clean Closed Won (P-11)
CloseDate 13, 100% 1 Date 2026-09-30 (P-11)
Tenant__c 13, 100% 1 Key, controlled 3 (P-11)

2.1.8 OpportunityLineItem (DATABP_SFDC_DBO.OPPORTUNITYLINEITEM), 13 rows

Grain: Id, 0 duplicates in 13 rows.

Column Populated Distinct Intent Values or distribution
Id 13, 100% 13 Key 18-character ids, prefix OLI
OpportunityId 13, 100% 13 Key one line item per Opportunity
Product2Id 13, 100% 2 Key 7 options, 6 equities
Quantity 13, 100% 1 Numeric count 10 on all 13: every license is 10 units in phase one (P-11)
UnitPrice 13, 100% 2 Numeric, dollars 40.00 seven times, 50.00 six; equals the product's price by code

2.1.9 usage_declaration (DATABP_USAGE_DBO.USAGE_DECLARATION), 12 rows

Grain: (tenant_id, declaration_id), 0 duplicates in 12 rows; (tenant_id, customer_id, product_code, usage_month) is also unique, 0 duplicates, so no report is restated in phase one.

Column Populated Distinct Intent Values or distribution
tenant_id 12, 100% 1 Key, controlled 3 (P-11)
declaration_id 12, 100% 12 Key 1 to 14, two numbers unused (PA9 and PA13, no report)
customer_id 12, 100% 12 Key 3 to 263
product_code 12, 100% 2 Controlled discrete, clean OPTIONS 7, EQUITIES 5; every value is a Product2 code (join 13)
usage_month 12, 100% 1 Date, first of the month 2026-10-01 (P-11)
declared_units 12, 100% 3 Numeric count 12 seven times, 10 four, 8 once; mean 11.00, standard deviation 1.35; no zeros
declared_at 12, 100% 1 Timestamp 2026-11-05 00:00 on all 12 (P-11)

2.1.10 client (DATABP_SRC_DBO.CLIENT), 20 rows

The data providers, DataBP's clients. Grain: client_id, 0 duplicates in 20 rows; no row marked deleted. Measured in Snowflake, 2026-11-19 19:39 UTC.

Column Populated Distinct Intent Values or distribution
client_id 20, 100% 20 Key 1 to 20
client_name 20, 100% 20 Label "Client 1" to "Client 20", except client 1, "Client 1 (changed 2026-11-18)", and client 2, "Client 2 (demo)" (P-13)

2.1.11 customer (DATABP_SRC_DBO.CUSTOMER), 5,000 rows

The subscribers, 250 under each data provider. Grain: (tenant_id, customer_id), 0 duplicates; customer_id alone is also unique, 0 duplicates. Measured in Snowflake, 19:39 UTC.

Column Populated Distinct Intent Values or distribution
tenant_id 5,000, 100% 20 Key 1 to 20, 250 rows each
customer_id 5,000, 100% 5,000 Key 1 to 5,000; tenant 3 holds 3 to 4,983
customer_name 5,000, 100% 5,000 Label, generated "Customer" and the customer_id on all 5,000 (P-14)
email 5,000, 100% 5,000 Contact, generated "c", the customer_id, "@example.com" on all 5,000 (P-14)
updated_at 5,000, 100% 5,000 Timestamp, near-unique 2026-11-12 00:40:04.691 to 00:42:13.279, the earlier build's load

2.1.12 invoice (DATABP_SRC_DBO.INVOICE), 20,008 rows

Invoice headers: 20,000 from the earlier build and phase one's 8. Grain: (tenant_id, invoice_id), 0 duplicates; invoice_id alone is also unique. 20,008 of 20,008 belong to a subscriber of their own data provider (join 2). Measured in Snowflake, 19:39 UTC.

Column Populated Distinct Intent Values or distribution
tenant_id 20,008, 100% 20 Key 1,000 per data provider; tenant 3 holds 1,008
invoice_id 20,008, 100% 20,008 Key 1 to 20,000, and 100001 to 100008
customer_id 20,008, 100% 5,000 Key every subscriber has invoices, 4 or 5 each
amount 20,008, 100% 1,000 Numeric, dollars min 10.00, P10 142.89, P25 348.39, median 689.52, P75 1,032.02, P90 1,237.52, max 1,374.52; mean 690.25, standard deviation 395.22; no zeros; a series stepping by 1.37 (P-14)
invoice_date 20,008, 100% 365 Date 2025-11-12 to 2026-11-11, 54 or 55 a day; 2026-10-31 has 63 with phase one's 8
status 20,008, 100% 4 Controlled discrete, clean open 5,008, overdue 5,000, paid 5,000, void 5,000; every month holds all four (P-15)
updated_at 20,008, 100% 20,008 Timestamp, near-unique 2026-11-12 00:42:13.412 to 2026-11-19 18:44:49.125

Only phase one's 8 invoices have items; the other 20,000 have none (P-15).

2.2 Overlap with existing sources

The three source systems carry some of the same facts twice; where both are populated they agree on every row in phase one. Counted in Snowflake, 2026-11-19 19:40 UTC.

Same fact, two places Agreement
Account Name and customer.customer_name, by Subscriber_Id__c 14 of 14 equal
Product2 Name and product.product_name, by product code 2 of 2 equal
Opportunity AccountId and its Contract's AccountId 13 of 13 equal
OpportunityLineItem UnitPrice and the product's unit_price 13 of 13 equal
invoice_item unit_price and the product's unit_price 8 of 8 equal
invoice amount and its item's amount, phase one's invoices 8 of 8 equal

Harbor holds none of these sources: the repository's dbt sources read only client (models/staging/_sources.yml), staged as stg_databp__client.

2.3 Machine-assisted analyses

NA: no column is a normalization candidate under section 11.2 of the standard. The only free-text columns with more than 50 distinct values, customer_name and email, follow one generated pattern on every row (P-14), so a synonym scan has nothing to find.

3. Profile results

Numbered P-1, P-2, ... in one series. An anomaly carries SOLUTION NEEDED and closes with RESOLVED, the resolver, the date, and the solution, in that order.

P-1. SOLUTION NEEDED. The design joins Salesforce's products to the platform's: the design document's source-to-target map (knowledge 111 item 806, section 6.1) joins a license to the platform through Product2.ProductCode, and the usage report names products by product_code (design sketch, item 805, section 8.4). The platform's product table, as designed in the sketch's section 8.2, has no product code: tenant_id, product_id, product_name, unit_price, updated_at. No designed column joins Product2 to product, so the reconciliation cannot compare a license or a usage report with an entitlement or an invoice item by product. RESOLVED, Ray Serrano, 2026-11-19 (answer 2a): the platform's product carries product_code, the code Salesforce's Product2.ProductCode and the usage report also carry; written into the design sketch (item 805, section 8.2) and the design document (item 806, section 6.1 and decision D-11).

P-2. SOLUTION NEEDED. Decision D-7 of the design document defines a license as a Contract with the line items of its won Opportunity. As designed (sketch, section 8.3), Contract carries Id, AccountId, StartDate, EndDate, ContractTerm, Status and Tenant__c, and Opportunity carries Id, AccountId, StageName, CloseDate and Tenant__c: no column joins a Contract to its Opportunity, so a Contract's licensed units cannot be found except by matching on the subscriber's Account alone. RESOLVED, Ray Serrano, 2026-11-19 (answer 1y): Opportunity carries ContractId, Salesforce's standard field for the contract associated with an opportunity (Salesforce object reference, read 2026-11-19); written into the design sketch (item 805, section 8.3) and the design document (item 806, section 6.1 and the evidence of decision D-7).

P-3. client, customer and invoice each declare a primary key: client (client_id); customer (tenant_id, customer_id); invoice (tenant_id, invoice_id). None declares a foreign key. Read from DATABP_SRC's information schema, 2026-11-19 16:29 UTC.

P-4. Every customer belongs to a client: customer.tenant_id = client.client_id matches 5,000 of 5,000 customers, and all 20 clients have customers. Counted 2026-11-19 16:30 UTC.

P-5. Every invoice belongs to a customer: invoice (tenant_id, customer_id) = customer (tenant_id, customer_id) matches 20,000 of 20,000 invoices, and all 5,000 customers have invoices. Counted 2026-11-19 16:30 UTC.

P-6. SOLUTION NEEDED. The reconciliation's paths, first round, by the reverse use of the Permutation Coverage Method (testing methodology, knowledge 2 item 83; Ray, 2026-11-19, answer 1y). Grain: one subscriber, one product, one month. Dimensions: each of the four documents (license, entitlement, usage report, invoice item) present or absent, and, where both sides are present, licensed against reported units, licensed against entitled units, and entitled against reported units, each less, equal or greater. Brute force: 80 combinations. Collapsed by which of the five checks fire (reported beyond licensed, entitled beyond licensed, billed without entitlement, entitled without billing, entitled beyond reported): 30 outcomes, 12 of which depend on three rules no design decision states: whether a usage report with no license is reported beyond licensed; whether an entitlement with no license is entitled beyond licensed; whether an entitlement with no usage report is entitled beyond reported. If an absent document counts as zero units, the 80 combinations collapse to 14 paths: no check fires; reported beyond licensed alone; with entitled beyond licensed; with that and entitled without billing; with those and entitled beyond reported; reported and entitled beyond licensed with entitled beyond reported; reported beyond licensed with billed without entitlement; with entitled without billing; entitled beyond licensed, entitled without billing and entitled beyond reported; entitled beyond licensed with entitled beyond reported; billed without entitlement alone; entitled without billing alone; with entitled beyond reported; entitled beyond reported alone. Not yet enumerated, for the second round: the join keys that do not match (Subscriber_Id__c, product_code), restated usage reports, the three changes after the close (design sketch, section 8.6), and each data provider seeing only its own rows. RESOLVED, Ray Serrano, 2026-11-19 (answer 1y): an absent document counts as zero units in every check (design document, item 806, decision D-12), which gives the 14 paths above. The second round's dimensions remain to be enumerated.

P-7. Phase one's rows, path by path (design decisions D-12 to D-15; Ray, 2026-11-19, answer 1y). One data provider, client 3 ("Client 3"), chosen because clients 1 and 2 carry the earlier demo's edits; one month, October 2026, the month of the design document's worked example; its first 14 subscribers by customer_id, read from DATABP_SRC on 2026-11-19 at 18:01 UTC; two products, created for phase one: the equities feed (product_code EQUITIES, 50 dollars a unit) and the options feed (OPTIONS, 40 dollars a unit), the worked example's prices. Each path's units are chosen so that exactly its checks fire, with an absent document counted as zero; billed units equal licensed units, or reported units where no license exists. The expected checks and dollars were computed from the units, not typed, and all 14 match the paths of P-6 (2026-11-19 18:02 UTC). Dollars: unbilled is units reported beyond licensed times the unit price; at risk is units entitled beyond reported times the unit price (design document, section 6.3).

Path Subscriber Product Licensed Entitled Reported Billed Checks that fire Dollars
PA1 3 equities 10 10 10 10 none none
PA2 23 options 10 10 12 10 reported beyond licensed unbilled 80
PA3 43 equities absent 12 12 12 reported beyond licensed, entitled beyond licensed unbilled 600
PA4 63 options 10 12 12 absent reported beyond licensed, entitled beyond licensed, entitled without billing unbilled 80
PA5 83 equities 10 14 12 absent reported beyond licensed, entitled beyond licensed, entitled without billing, entitled beyond reported unbilled 100, at risk 100
PA6 103 options 10 14 12 10 reported beyond licensed, entitled beyond licensed, entitled beyond reported unbilled 80, at risk 80
PA7 123 equities 10 absent 12 10 reported beyond licensed, billed without entitlement unbilled 100
PA8 143 options 10 10 12 absent reported beyond licensed, entitled without billing unbilled 80
PA9 163 equities 10 12 absent absent entitled beyond licensed, entitled without billing, entitled beyond reported at risk 600
PA10 183 options 10 12 10 10 entitled beyond licensed, entitled beyond reported at risk 80
PA11 203 equities 10 absent 10 10 billed without entitlement none
PA12 223 options 10 10 10 absent entitled without billing none
PA13 243 equities 10 10 absent absent entitled without billing, entitled beyond reported at risk 500
PA14 263 options 10 10 8 10 entitled beyond reported at risk 80

Rows, 97 in all: product 2; Product2 2 (ProductCode EQUITIES and OPTIONS, Tenant__c 3); Account 14, one per subscriber (Subscriber_Id__c the customer_id, Tenant__c 3); Opportunity 13, one per path with a license, StageName Closed Won (the won stage as a third-party description of Salesforce's opportunity stages names it, CData; stage names are each Salesforce organization's own), CloseDate 2026-09-30, ContractId its Contract; OpportunityLineItem 13 (Quantity the licensed units, UnitPrice the product's price); Contract 13 (StartDate 2026-10-01, ContractTerm 12, EndDate 2027-09-30, Status Activated, one of the Contract status values in Salesforce's object reference); entitlement 12 (start 2026-10-01, end 2027-09-30); usage_declaration 12 (usage_month 2026-10, declared_at 2026-11-05); invoice 8 and invoice_item 8 (invoice_date 2026-10-31, status open, a value today's invoices use; invoice_id from 100001, above data provider 3's highest, 19,983; amount the item's units times its price). Salesforce ids are 18-character ids from a fixed seed. The answer key holds the 14 rows of the table above, in databp-dbt beside the models (D-8, D-14).

P-8. Every designed table has the grain the design gives it: 0 duplicates on each key, and on each business key the reconciliation groups by (sections 2.1.1 to 2.1.9). Counted in Snowflake, 2026-11-19 19:28 UTC.

P-9. Every designed join matches all its rows, at most one row per row, so each hop is many-to-one or one-to-one as drawn. Counted in Snowflake, 19:29 UTC, except joins 3, 11 and 12, counted in SQL Server at 19:30 UTC (see P-10).

Join Rows matched Cardinality
3 entitlement to customer 12 of 12 many to one
4 entitlement to product 12 of 12 many to one
5 invoice_item to invoice 8 of 8 one to one in phase one
6 invoice_item to product 8 of 8 many to one
7 Opportunity to Account 13 of 13 many to one
8 OpportunityLineItem to Opportunity 13 of 13 one to one in phase one
9 OpportunityLineItem to Product2 13 of 13 many to one
10 Contract to Account 13 of 13 many to one
11 Account to customer 14 of 14 one to one
12 usage_declaration to customer 12 of 12 many to one
13 usage_declaration to Product2 12 of 12 many to one
14 Opportunity to Contract 13 of 13; 13 of 13 Contracts have one one to one
15 Product2 to product 2 of 2 one to one

P-10. SOLUTION NEEDED. The connector does not copy DATABP_SRC.dbo.customer to Snowflake: its table list (tutorial step 26) names client, invoice and the nine designed tables, and Snowflake refuses DATABP_LAB.DATABP_SRC_DBO.CUSTOMER as not existing (19:28 UTC). Joins 3, 11 and 12 reach customer, the subscriber every check is reported for, so the pipeline cannot make them, and the subscriber's name is not available downstream. Proposed: add DATABP_SRC.dbo.customer to the connector's table list. RESOLVED, Ray Serrano, 2026-11-19 (answer 1y): DATABP_SRC.dbo.customer added to the connector's table list at about 19:35 UTC (tutorial step 26); DATABP_LAB.DATABP_SRC_DBO.CUSTOMER holds 5,000 rows, SQL Server's count, at 19:38:01 UTC, and joins 3, 11 and 12 measured on the Snowflake copies at 19:38:16 UTC match as in SQL Server: 12 of 12, 14 of 14 and 12 of 12, at most one row each.

P-11. Columns that hold one value in phase one, by the phase's scope and not by a defect: every tenant column (one data provider); Contract StartDate, EndDate, ContractTerm and Status, Opportunity StageName and CloseDate, entitlement start_date and end_date, usage_month and declared_at (one month, one contract shape, one reporting date); OpportunityLineItem Quantity (every license 10 units); Account OwnerId (one owner); invoice_item item_id (one item per invoice). The reversal risk "single-value columns masquerading as dimensions" (Profiling standard, section 4) does not apply to them as source columns; it applies to any check or chart that relies on their variety, which phase one cannot show. Later phases vary them where the method's later rounds need it.

P-12. The reconciliation works on the Snowflake copies: the generator's verify query, run on DATABP_LAB's three schemas, derives 14 rows, and all 14 match the answer key's five checks (2026-11-19 19:30:17 UTC). The copies therefore carry every value the checks read, and the data reaches the warehouse unchanged for the reconciliation's purposes.

P-13. Test contamination, named: client 1's name is "Client 1 (changed 2026-11-18)" and client 2's is "Client 2 (demo)", the earlier demo's edits that P-7 notes. The other 18 names follow "Client" and the client_id. Phase one uses client 3, so the app's figures are untouched; a demo showing the client list would show the two edits.

P-14. The existing tables are generated, not real: customer_name is "Customer" and the customer_id on 5,000 of 5,000 rows, email is "c", the customer_id, "@example.com" on 5,000 of 5,000, invoice amounts are 1,000 values stepping by 1.37 from 10.00 to 1,374.52, about 20 invoices each, and invoice dates run 54 or 55 a day for a year with the four statuses in every month. Counted in Snowflake, 2026-11-19 19:40 UTC. No free-text column holds anything but its pattern.

P-15. SOLUTION NEEDED. Two questions about what counts as billed. First, invoice status: void appears on 5,000 invoices, and the reconciliation's billing (the generator's verify query) counts every item whatever its invoice's status; a void invoice is presumably not billing, but no decision says so. Second, the 20,000 existing invoices have no items, so billing read from items ignores them; among them 5 are October 2026 invoices of data provider 3 for phase-one subscribers (invoice_id 23, 5123, 5143, 10243 and 15003, for subscribers 23, 123, 143, 243 and 3), all void. Phase one is unaffected either way, since its 8 invoices are open and itemized, and the 5 are void and carry no items. Proposed: billing counts the items of invoices whose status is not void, and an invoice with no items is not billing. RESOLVED, Ray Serrano, 2026-11-19 (answer 1y): billing counts only the items of invoices whose status is not void, and an invoice with no items is not billing (design document, item 806, decision D-16); invoice.status integrates (section 6.1).

P-16. SOLUTION NEEDED. The app shows what changed since the last month-end close (design, D-2), which needs to know when a source row changed. Two places hold it: each source table's updated_at, and the connector's journal tables in Snowflake with its _SNOWFLAKE_UPDATED_AT. No decision names which the design reads, so the updated_at columns are deferred until it does (section 6.2). RESOLVED, Ray Serrano, 2026-11-19 (answer 3b): change times are read from each source table's updated_at (design document, item 806, decision D-17); the five updated_at columns integrate (section 6.1).

4. Cleansing advice for source administration

The source owner is DataBP's own demo team, since the sources are generated.

Problem Impact Recommendation
Clients 1 and 2 carry demo edits in their names (P-13) A client list shown in the demo reads "(changed 2026-11-18)" and "(demo)" Restore both names, or keep them and say why when shown

5. Integration actions

Integrate now, as the design's source-to-target map (design, section 6.1) places them: the 63 columns of section 6.1 below. Not loaded: the 7 columns of section 6.3. Each verdict's check is input to the design's testing plan (design, section 8, checks from the profile).

6. Verdict summary

Each verdict names its check. For a profile of the platform's own surfaces, the verdicts read as fitness: fit, fit under named conditions, unfit. Here every source is designed, so Integrate reads as fit for the reconciliation.

6.1 Integrate

63 columns; each row of the appendix marked Integrate names its concept and check. By table:

Table Columns, and the concept they integrate
client client_id, client_name: the data provider
customer tenant_id, customer_id, customer_name, updated_at: the subscriber under its data provider, and when it last changed
invoice tenant_id, invoice_id, customer_id, amount, invoice_date, status, updated_at: the invoice header, whether it bills (not void, D-16), and when it last changed
product tenant_id, product_id, product_code, product_name, unit_price, updated_at: the data product, and when it last changed
entitlement tenant_id, entitlement_id, customer_id, product_id, units, start_date, end_date, updated_at: entitled units per period, and when they last changed
invoice_item tenant_id, invoice_id, item_id, product_id, units, unit_price, amount, updated_at: billed units, and when they last changed
Account Id, Tenant__c, Subscriber_Id__c: the subscriber in Salesforce, joined to the platform
Product2 Id, ProductCode, Tenant__c: the product in Salesforce, joined by code
Contract Id, AccountId, StartDate, EndDate, Status, Tenant__c: the license and its period
Opportunity Id, ContractId, StageName, Tenant__c: the won Opportunity behind a license
OpportunityLineItem Id, OpportunityId, Product2Id, Quantity, UnitPrice: licensed units per product
usage_declaration tenant_id, declaration_id, customer_id, product_code, usage_month, declared_units, declared_at: reported units per month

6.2 Defer

None: P-15 and P-16 are resolved (design decisions D-16 and D-17), and no column waits on a condition.

6.3 Reject

Column Reason
customer.email Not used by the app; the design's map does not carry it (design, section 6.1)
Account.Name Structural duplicate of customer.customer_name, equal on 14 of 14 (section 2.2)
Account.OwnerId Not used by the app; one value in phase one
Product2.Name Structural duplicate of product.product_name, equal on 2 of 2 (section 2.2)
Contract.ContractTerm Not used; the license period is StartDate to EndDate
Opportunity.AccountId Structural duplicate of its Contract's AccountId, equal on 13 of 13 (section 2.2)
Opportunity.CloseDate Not used by the reconciliation

Appendix — Column inventory

Populated and distinct counts from Snowflake, 2026-11-19 19:27 to 19:40 UTC. Discipline tier applies to controlled columns only; NA elsewhere.

# Column Populated % Distinct Field type Discipline tier Reversal risks Verdict Reason Check
1 client.client_id 20 100 20 Key NA None Integrate The data provider's identifier grain-unique
2 client.client_name 20 100 20 Label NA Test contamination, P-13 Integrate The data provider's name; clients 1 and 2 carry demo edits, outside phase one not-null
3 customer.tenant_id 5,000 100 20 Key NA None Integrate The subscriber's data provider relationship to client, join 1
4 customer.customer_id 5,000 100 5,000 Key NA None Integrate The subscriber's identifier grain-unique with tenant_id
5 customer.customer_name 5,000 100 5,000 Label NA None Integrate The subscriber's name the app shows not-null
6 customer.email 5,000 100 5,000 Contact NA None Reject Not used by the app; not in the design's map None: not loaded
7 customer.updated_at 5,000 100 5,000 Timestamp NA None Integrate When the source last changed the row (D-17) null-slice bound: 0 nulls
8 invoice.tenant_id 20,008 100 20 Key NA None Integrate The invoice's data provider relationship to client
9 invoice.invoice_id 20,008 100 20,008 Key NA None Integrate The invoice's identifier grain-unique with tenant_id
10 invoice.customer_id 20,008 100 5,000 Key NA None Integrate The invoiced subscriber relationship to customer, join 2
11 invoice.amount 20,008 100 1,000 Numeric, dollars NA None Integrate The invoice total equals the sum of its items where items exist
12 invoice.invoice_date 20,008 100 365 Date NA None Integrate The billing date, which places an item in its month not-null
13 invoice.status 20,008 100 4 Controlled discrete Clean None Integrate Whether the invoice bills: void does not (P-15, D-16) vocabulary-exact: open, overdue, paid, void
14 invoice.updated_at 20,008 100 20,008 Timestamp NA None Integrate When the source last changed the row (D-17) null-slice bound: 0 nulls
15 product.tenant_id 2 100 1 Key NA None Integrate The product's data provider relationship to client
16 product.product_id 2 100 2 Key NA None Integrate The product's identifier grain-unique with tenant_id
17 product.product_code 2 100 2 Controlled discrete Clean None Integrate The code shared with Salesforce and the usage report unique per data provider; matched by Product2, join 15
18 product.product_name 2 100 2 Label NA None Integrate The product's name the app shows not-null
19 product.unit_price 2 100 2 Numeric, dollars NA None Integrate The price that turns units into dollars greater than zero
20 product.updated_at 2 100 2 Timestamp NA None Integrate When the source last changed the row (D-17) null-slice bound: 0 nulls
21 entitlement.tenant_id 12 100 1 Key NA Single value in phase one, P-11 Integrate The entitlement's data provider relationship to client
22 entitlement.entitlement_id 12 100 12 Key NA None Integrate The entitlement's identifier grain-unique with tenant_id
23 entitlement.customer_id 12 100 12 Key NA None Integrate The entitled subscriber relationship to customer, join 3
24 entitlement.product_id 12 100 2 Key NA None Integrate The entitled product relationship to product, join 4
25 entitlement.units 12 100 3 Numeric count NA None Integrate Entitled units greater than zero
26 entitlement.start_date 12 100 1 Date NA Single value, P-11 Integrate Start of the entitled period not after end_date
27 entitlement.end_date 12 100 1 Date NA Single value, P-11 Integrate End of the entitled period not before start_date
28 entitlement.updated_at 12 100 12 Timestamp NA None Integrate When the source last changed the row (D-17) null-slice bound: 0 nulls
29 invoice_item.tenant_id 8 100 1 Key NA Single value, P-11 Integrate The item's data provider relationship to client
30 invoice_item.invoice_id 8 100 8 Key NA None Integrate The item's invoice relationship to invoice, join 5
31 invoice_item.item_id 8 100 1 Key NA Single value, P-11 Integrate The item's number within its invoice grain-unique with tenant_id and invoice_id
32 invoice_item.product_id 8 100 2 Key NA None Integrate The billed product relationship to product, join 6
33 invoice_item.units 8 100 2 Numeric count NA None Integrate Billed units greater than zero
34 invoice_item.unit_price 8 100 2 Numeric, dollars NA None Integrate The billed price greater than zero
35 invoice_item.amount 8 100 3 Numeric, dollars NA None Integrate The billed amount equals units times unit_price
36 invoice_item.updated_at 8 100 8 Timestamp NA None Integrate When the source last changed the row (D-17) null-slice bound: 0 nulls
37 Account.Id 14 100 14 Key NA None Integrate The subscriber's Salesforce identifier grain-unique
38 Account.Name 14 100 14 Label NA Same concept, different form Reject Duplicate of customer.customer_name, 14 of 14 equal None: not loaded
39 Account.OwnerId 14 100 1 Key NA Single value, P-11 Reject Not used by the app None: not loaded
40 Account.Tenant__c 14 100 1 Key NA Single value, P-11 Integrate The subscriber's data provider in Salesforce relationship to customer, join 11
41 Account.Subscriber_Id__c 14 100 14 Key NA None Integrate The platform's subscriber, carried in Salesforce unique per data provider; join 11
42 Product2.Id 2 100 2 Key NA None Integrate The product's Salesforce identifier grain-unique
43 Product2.Name 2 100 2 Label NA Same concept, different form Reject Duplicate of product.product_name, 2 of 2 equal None: not loaded
44 Product2.ProductCode 2 100 2 Controlled discrete Clean None Integrate The product code that joins Salesforce to the platform relationship to product, join 15
45 Product2.Tenant__c 2 100 1 Key NA Single value, P-11 Integrate The product's data provider in Salesforce relationship to client
46 Contract.Id 13 100 13 Key NA None Integrate The license's identifier grain-unique
47 Contract.AccountId 13 100 13 Key NA None Integrate The licensed subscriber relationship to Account, join 10
48 Contract.StartDate 13 100 1 Date NA Single value, P-11 Integrate Start of the license not after EndDate
49 Contract.EndDate 13 100 1 Date NA Single value, P-11 Integrate End of the license not before StartDate
50 Contract.ContractTerm 13 100 1 Numeric, months NA Single value, P-11 Reject Not used; the period is StartDate to EndDate None: not loaded
51 Contract.Status 13 100 1 Controlled discrete Clean Single value, P-11 Integrate Whether the license is in force vocabulary-exact
52 Contract.Tenant__c 13 100 1 Key NA Single value, P-11 Integrate The license's data provider equals its Account's Tenant__c
53 Opportunity.Id 13 100 13 Key NA None Integrate The won Opportunity's identifier grain-unique
54 Opportunity.AccountId 13 100 13 Key NA Same concept, different form Reject Duplicate of its Contract's AccountId, 13 of 13 equal None: not loaded
55 Opportunity.ContractId 13 100 13 Key NA None Integrate The license it belongs to relationship to Contract, join 14
56 Opportunity.StageName 13 100 1 Controlled discrete Clean Single value, P-11 Integrate Whether the Opportunity is won vocabulary-exact
57 Opportunity.CloseDate 13 100 1 Date NA Single value, P-11 Reject Not used by the reconciliation None: not loaded
58 Opportunity.Tenant__c 13 100 1 Key NA Single value, P-11 Integrate The Opportunity's data provider equals its Contract's Tenant__c
59 OpportunityLineItem.Id 13 100 13 Key NA None Integrate The line item's identifier grain-unique
60 OpportunityLineItem.OpportunityId 13 100 13 Key NA None Integrate The line item's Opportunity relationship to Opportunity, join 8
61 OpportunityLineItem.Product2Id 13 100 2 Key NA None Integrate The licensed product relationship to Product2, join 9
62 OpportunityLineItem.Quantity 13 100 1 Numeric count NA Single value, P-11 Integrate Licensed units greater than zero
63 OpportunityLineItem.UnitPrice 13 100 2 Numeric, dollars NA None Integrate The licensed price greater than zero
64 usage_declaration.tenant_id 12 100 1 Key NA Single value, P-11 Integrate The report's data provider relationship to client
65 usage_declaration.declaration_id 12 100 12 Key NA None Integrate The report's identifier grain-unique with tenant_id
66 usage_declaration.customer_id 12 100 12 Key NA None Integrate The reporting subscriber relationship to customer, join 12
67 usage_declaration.product_code 12 100 2 Controlled discrete Clean None Integrate The reported product relationship to Product2, join 13
68 usage_declaration.usage_month 12 100 1 Date NA Single value, P-11 Integrate The month reported first day of a month
69 usage_declaration.declared_units 12 100 3 Numeric count NA None Integrate Reported units zero or more
70 usage_declaration.declared_at 12 100 1 Timestamp NA Single value, P-11 Integrate When reported; the latest report counts not-null

Compliance record

Built by the author last, before the document is presented for agreement (Standard: Branch Delivery Documents, K#12 I#27, "Compliance record before agreement"): every section and field of this template shown present and filled, by infra/workstation/pilot/compliance_sections.py; every rule of that standard and of the standards it cites, each with the passage that meets it or marked NOT MET; and the decisions the document carries. While this section reads NOT BUILT, the document is not presented for agreement.

NOT BUILT.