Page Comparison

id

internally generate id/index. Joins the header to it’s relevant lines

000000053081868a04

invoice_line__c.invoice__r

identifier__c

the invoice number in the source system (usually the unique invoice number but may be an internal index number)

336455

????????

is_deleted

true/false/null

true/false

issue_date_time__c

Date invoice was issued to customer

2013-01-03 04:41:39

last_modified_date

Date invoice was modified

2013-01-03 04:41:39

created_date

internal date when created in slyncy

legal_monetary_total__c

Total tax inclusive value of invoice

$110.10

name

Inconsistently used and customer name is better to get from parties__c table

note__c

field is not currently used

large varchar field of 32678 chars

owner_id

The internal ID of the Slyncy datahub

000000000000069dfa

All tables have an owner_id, this associates the data with the connector

referenceid__c

field is not currently used

status__c

field to indicate if invoice is finalized or not. Usually only finalized invoices are imported.

COMPLETED

tags__c

indicates which splitter data belongs to if data gets split

branch1

accountingcustomerparty__r

the party that is responsible for paying the invoice (human)

0000000535418915c7

party__c.id

customercontact__r

The party that the invoice relates to (patient). Inconsistently used as it is often impossible to trace mixed patient invoices to a single patient

00000000057152066c

party__c.id

relatedtransaction__r

inconsistently used

tax_total__c

The amount of tax payable on the invoice. Not currently used

customer_code__c

seems to be used to generate internal hashes

client_key

primary key coming from source system, if it exists, otherwise a combination of fields to create a unique hash. Allows for internal identification of update vs insert

source_id

Used to trace back to original record if splitters - internal use only

invoice__c.id on the source of the split hub