An entry is used to hold all relevant information with regard to a certain amount of money owed to or requested by a business partner (debtor, creditor). The entry is always created from a source called statement.
||Text(255)||The name of the customer account.|
||Lookup(Account)||The associated account.|
||Currency(16, 2)||Outstanding amount this entry refers to. Zero if the entry is balanced.|
||Text(255)||The number of the business partner, i.e. debtor number or creditor number.|
||Picklist||Type of the business partner, i.e. debtor or creditor.
||Lookup(BusinessEntity__c)||The business entity this entry relates to.|
||Lookup(Contact)||The associated contact|
||Picklist||Approval processes for outgoing money transfers
||LongTextArea(32768)||SEPA validation error messages.|
||SUM(EntryItem__c.ExpectedAmount__c)||The aggregated currently expected amount for pending payments (sum over all entry items): positive value if it is a payout, negative value if it is a payment|
||Checkbox||The field is checked if Entry has SEPA validation errors.|
||Currency(18, 0)||The initial amount, positive value for type Debit, negative value for type Credit|
||Currency(16, 2)||The overall open amount. Positive value if it is a debit, negative value if it is a credit.|
||Currency(16, 2)||The currently payable amount as the sum of outstanding and expected amount|
||Date||Date of the last payment which set the status of the entry to Balanced.|
||Text(255)||Describes the purpose of a SEPA transaction (direct debit, credit transfer) or credit card statement|
|Requested Bank Account||
||Lookup(BankAccount__c)||The bank account that should be used when creating SEPA XML Credit Transfer files (when no mandate is available).|
|Requested Payment Instrument||
||Lookup(PaymentInstrument__c)||Restricts the payment process to this particular payment instrument (e.g. credit card token, SEPA mandate). The payment instrument must be related to the selected account.|
|Requested Payment Method||
||Picklist||The requested payment method indicates how the money should flow. This is not binding for the customer, but can be used to aid further business processes.
|Requested Payment Provider||
||Lookup(PaymentProvider__c)||Restricts the payment process to this particular provider|
|Service Period End||
||Date||End of the effective service period for this entry.|
|Service Period Start||
||Date||Start of the effective service period for this entry.|
||SUM(EntryItem__c.Amount__c)||The currently settled amount. Positive value if it is a payout, negative value if it is a payment.|
||Date||The effective date of the statement (e.g. invoice date).|
||Text(255)||Describes the original statement for a quick overview. This is treated a an internal note.|
|Statement Distribution URL||
||Url||Public link to the statement, usually a PDF file link|
||Text(255)||External ID of the original document|
||Text(255)||An unique number identifying the originating record. Could be an invoice number or order number.|
|Statement Payment Due Date||
||Date||The payment due date of the statement (e.g. StatementDate + PaymentTerms).|
||Picklist||The statement type reflects the business process leading to this particular entry.
||Picklist||Indicate whether the statement refers to an open or balanced-out claim.
||Text(255)||Descriptive name for the entry, which can be used in communication to the customer.|
||Picklist||Distinguish debit and credit entries.