How To Use Finnish Bankersa
|
|
|
- Hilda Clarissa Powell
- 5 years ago
- Views:
Transcription
1 <?xml version="1.0" encoding="iso "?> <!-- Copyright Tieto Oyj--> <!-- TEAPPSXML-description version INVOICES --> <!-- In this document first is description of element and after that element name with possible attributes--> <INVOICE_CENTER> <!-- Transportframe, which is using to routing and confirming --> <TRANSPORT_FRAME> <!-- Frame's version: TF01 as constant data --> <TF_CODE/> <!-- Timestamp, created time of batch, in format yyyymmddhhmmss --> <TIMESTAMP/> <!-- Identifying code of batch, given by sender --> <BATCH_ID/> <!-- Receivers data --> <CONTENT_RECEIVER> <!-- Receiver's Net Service identifier in a service offered by a receiving operation --> <RECEIVER_REF/> <!-- Receiver's operator --> <INTERMEDIATOR/> <!-- Identifying of batch, could be a same value as TRANSPORT_FRAME/BATCH_ID and CONTENT_FRAME/BLOCK_ID --> <CONTENT_REF/> </CONTENT_RECEIVER> <!-- Sender, batch sender's Net Service identifier in a receiving service/operator --> <SENDER/> <!-- Sender's operator --> <INTERMEDIATOR/> <!-- Senders domain-name --> <SENDER_DOMAIN/> <!-- Do you want confirmation/actual confirmation from batch: 0 = no, 1 = yes, 2 = actual receipt --> <FB_REQUEST/> <!-- Receipt of linetransfer : POS = transfer successful, NEG = transfer unsuccessful --> <REQUEST_MESSAGE/> <!-- Message to acknowledgement receiver --> <REQUEST_TEXT/> <!-- Summary part --> <TF_SUMMARY> <!-- Events quantity in batch --> <COUNT/> <TOTAL> <!-- Total summary of events currency amount in batch --> </TOTAL> <!-- Batch size in bytes, the total size in bytes of all unzipped files --> <BATCH_SIZE/> </TF_SUMMARY> </TRANSPORT_FRAME> <!-- Contentframe, where is an actual event-material. One contentframe contains only one event type (for example. invoice) --> <CONTENT_FRAME> <!-- Frame's version: CF01 as constant data, mandatory --> <CF_CODE/> <!-- Sender's Net Service identifier in a receivers service, mandatory --> <NET_SERVICE_ID/> <!-- Sender's operator --> <INTERMEDIATOR/> <!-- Senders domain-name --> <SENDER_DOMAIN/> <!-- Identifying data of batch, code, giving by a sender (for example filename ), mandatory --> <BLOCK_ID/> <!-- Timestamp (created time), mandatory, in format yyyymmddhhmmss --> <TIMESTAMP/> <BLOCK_RULES> 1(45)
2 <!-- Transaction type: 00 = invoice, mandatory --> <TRANSACTION_TYPE/> <!-- Action: 00 = addition, mandatory --> <BLOCK_ACTION/> <!-- Batch-specific method of interchange: 01 = printing of sales invoice --> <BLOCK_METHOD/> <!-- Data format: value is TEAPPSXML, when data is valid against Invoicecenter's XML- description, mandatory --> <BLOCK_FORMAT/> <!-- TEAPPSXML-description version --> <FORMAT_VERSION/> <!-- Used character set: ISO (For the moment only supported) --> <CHARACTER_SET/> </BLOCK_RULES> <!-- Data needed by archiving --> <BLOCK_DEFAULTS> <!-- Archive identifiers. ARCHIVE_TYPE -attribute optional, others mandatory --> <ARCHIVE_INFO SOURCE_SYSTEM="" DOCUMENT_TYPE="" ARCHIVE_ORG_ID="" YEAR_ID="" ARCHIVE_BLOCK="" ARCHIVE_TYPE=""/> <!-- Data needed by printing service --> <BLOCK_PRINTING> <!-- Printing Service/eLetter printing control --> <E-KIRJE> <!-- Electronic archive: T = only printing, B = printing and archive, C = only archive --> <APM_ARCHIVE/> <!-- Service action: 0 = normal, E = special work, T = test print, J = transfer test, no printing --> <SERVICE_ACTIONS/> <!-- Letter class: 1 = 1.class letter or 2 = 2.class letter --> <LETTER_CLASS/> <!-- Archive application id --> <APM_ARCHIVE_CODE/> <!-- Cover page template id --> <FORM_FIRST_PAGE/> <!-- Continuation page template id --> <FORM_CONT_PAGE/> <!-- Specification page template id --> <FORM_SPEC_PAGE/> <!-- Advance announcement cover page id --> <ADVANCED_NOTICE_FIRST_PAGE/> <!-- Advance announcement continuation page id --> <ADVANCED_NOTICE_CONT_PAGE/> <!-- Advance announcement specification page id --> <ADVANCED_NOTICE_SPEC_PAGE/> </E-KIRJE> </BLOCK_PRINTING> </BLOCK_DEFAULTS> <BLOCK_SUMMARY> <!-- Messages/events quantity in batch --> <COUNT/> <!-- Event total currency amount in batch, all events summarized --> <TOTAL> </TOTAL> </BLOCK_SUMMARY> <LINKS> <!-- Link, optional attributes TYPE and OBJECT --> <LINK TYPE="" OBJECT=""/> </LINKS> 2(45)
3 <!-- Sales invoices --> <INVOICES> <INVOICE> <!-- Control part, optional --> <CONTROL> <!-- Archive information --> <ARCHIVE_CONTROL> <!-- Supplier id --> <SUPPLIER_ID/> <!-- Supplier name --> <SUPPLIER_NAME/> <!-- Period id --> <PERIOD_ID/> <!-- Customer id --> <CUSTOMER_ID/> <!-- Customer name --> <CUSTOMER_NAME/> <!-- Identifier --> <IDENTIFIER_ID/> <!-- Group id --> <GROUP_ID/> <!-- Payment blocked --> <PAYMENT_BLOCKED/> <!-- Supplier group --> <SUPPLIER_GROUP/> <!-- Event type --> <EVENT_TYPE/> <!-- Order number --> <AGREEMENT_NO/> <!-- Status code --> <STATUS_ID/> <!-- Invoice period --> <INVOICE_MONTH/> <INVOICE_CENTURY/> <INVOICE_DECADE_AND_YEAR/> <!-- Invoice VAT period --> <VAT_SEASON> </VAT_SEASON> <!-- Ledger code type --> <LEDGER_DIMENSION_TYPE/> <!-- Ledger code --> <LEDGER_DIMENSION_ID/> <!-- Voucher serie --> <VOUCHER_SERIE/> <!-- Voucher number --> <VOUCHER_NUMBER/> <!-- Voucher date --> <VOUCHER_DAY/> <VOUCHER_MONTH/> <VOUCHER_CENTURY/> <VOUCHER_DECADE_AND_YEAR/> <!-- Sent advance invoice?, 0 or empty = no, 1 = advance invoice sent --> <SECOND_TRANSFER/> <!-- Bookkeeping control dimensions --> <DIMENSIONS> <DIMENSION> <LEVEL TITLE=""/> <DIMENSION_VALUE DIMENSION_LENGTH=""/> <DIMENSION_NAME/> </DIMENSION> </DIMENSIONS> 3(45)
4 <!-- Control stamp --> <CONTROL_STAMP> <CONTROL_DATE> </CONTROL_DATE> <CONTROL_USER/> </CONTROL_STAMP> <!-- Acceptance stamp --> <ACCEPTANCE_STAMP> <ACCEPTANCE_DATE> </ACCEPTANCE_DATE> <ACCEPT_USER/> </ACCEPTANCE_STAMP> <!-- Bank account number --> <BANK_ACCOUNT_NUMBER/> <!-- International IBAN bank account number --> <IBAN_ACCOUNT_NUMBER/> <!-- Bank international name --> <SWIFT_CODE/> <!-- Secrecy class --> <SECRECY_CLASS/> <!-- Proposed payment date --> <PAYMENT_DATE_PROPOSAL> </PAYMENT_DATE_PROPOSAL> <!-- Organisation code --> <ORGANIZATION_CODE/> <!-- Delivery completed --> <DELIVERY_COMPLETED/> </ARCHIVE_CONTROL> <!-- Payment transaction information --> <PAYMENT_TRANSACTIONS> <PAYMENT_TRANSACTION> <!-- Voucher serie --> <VOUCHER_SERIE/> <!-- Voucher number --> <VOUCHER_NUMBER/> <!-- Bookkeeping money account --> <CHARGE_ACCOUNT/> <!-- Payment date --> <PAYMENT_DATE> </PAYMENT_DATE> 4(45)
5 <!-- Payment sum --> <PAYMENT_TOTAL> </PAYMENT_TOTAL> <!-- Payee bank information --> <PAYEE_BANKS> <BANK_NAME/> <BANK_ACCOUNT_NUMBER/> <SWIFT_CODE/> <IBAN_ACCOUNT_NUMBER/> </PAYEE_BANKS> <!-- Payer bank information --> <PAYER_BANKS> <BANK_NAME/> <BANK_ACCOUNT_NUMBER/> <SWIFT_CODE/> <IBAN_ACCOUNT_NUMBER/> </PAYER_BANKS> <!-- Transaction date, voucher date --> <TRANSACTION_DATE> </TRANSACTION_DATE> <!-- Payment transaction creator information --> <USER> <!-- ID --> <ID/> <!-- Name --> <NAME/> </USER> <!-- Internal key --> <IDENTIFIER_ID/> </PAYMENT_TRANSACTION> </PAYMENT_TRANSACTIONS> <!-- Controls related with images and appendixes --> <!-- TYPE-attribute defines appendix type, alternatives: INVOICE_IMAGE (= image), VOUCHER_MEMO (= other appendix) or SCANNED (= scanned image), SIGNATURE_VALIDATION (= validation file), SIGNATURE (= separate signature file), INVOICE_DATA (= original file), mandatory --> <!-- SOURCE-attribute defines appendix source, alternatives: ORIGINAL (= payee created image or appendix), IC_IMAGE (= InvoiceCenter created invoice image) or IC (= InvoiceCenter created attachment), optional --> <!-- SIGNED-attribute defines type of signature, alternatives: YES (= signed, details of type missing), XADES (= signed with type XADES), CADES (= signed with type CADES) or NO (= not signed), optional --> <IMAGE_CONTROL TYPE="" SOURCE="" SIGNED=""> <!-- Directory name --> <IMAGE_DIRECTORY/> <!-- File name including extension, in optional IMAGE_TYPE -attribute one should provide file type if it is different from extension --> <IMAGE_FILE IMAGE_TYPE=""/> <!-- Conversion/Image-processing program name --> <IMAGE_PROGRAM/> <!-- Description of attachment --> <IMAGE_DESCRIPTION/> </IMAGE_CONTROL> <!-- Control related with payment, not in use--> <PAYMENT_CONTROL/> <!-- Travel-payment controls --> <TRAVEL_CONTROL> <!-- Trip id --> 5(45)
6 <TRAVEL_ID/> <!-- Trip type, optional attribute CODE --> <TRAVEL_TYPE CODE=""/> <!-- Trip specifier --> <TRAVEL_INFO/> <!-- Voucher description, optional attribute CODE --> <VOUCHER_TITLE CODE=""/> <!-- Allowance class information --> <INVOICING_BASE> <!-- Allowance class --> <ALLOWANCE_CLASS/> <!-- Allowance class name --> <ALLOWANCE_NAME/> </INVOICING_BASE> <!-- Financing information --> <FINANCE> <FINANCE_INFO> <!-- Type --> <FINANCE_TYPE/> <!-- Date --> <!-- Description --> <EXPLANATION/> <!-- Sum, mandatory VAT -attribute --> <FINANCE_AMOUNT> </FINANCE_AMOUNT> </FINANCE_INFO> </FINANCE> <!-- Full cost estimate, mandatory VAT -attribute --> <TOTAL_COST_ESTIMATION> </TOTAL_COST_ESTIMATION> <!-- Invoicer/Invoice creator --> <INVOICE_MAKER> <STAMP> <!-- Stamp creator --> <USER> <ID/> <NAME/> </USER> <!-- Time stamp --> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> <!-- Note information --> <NOTE/> <!-- Status information --> <STATUS/> <!-- Next stamp creator --> <NEXT_USER> 6(45)
7 <ID/> <NAME/> </NEXT_USER> </STAMP> </INVOICE_MAKER> <!-- Approval information --> <APPROVAL> <STAMP> <!-- Stamp creator --> <USER> <ID/> <NAME/> </USER> <!-- Time stamp --> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> <!-- Note information --> <NOTE/> <!-- Status information --> <STATUS/> <!-- Next stamp creator --> <NEXT_USER> <ID/> <NAME/> </NEXT_USER> </STAMP> </APPROVAL> <!-- Handler --> <FIXED_OPERATOR> <STAMP> <!-- Stamp creator --> <USER> <ID/> <NAME/> </USER> <!-- Time stamp --> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> <!-- Note information --> <NOTE/> <!-- Status information --> <STATUS/> <!-- Next stamp creator --> <NEXT_USER> <ID/> <NAME/> 7(45)
8 </NEXT_USER> </STAMP> </FIXED_OPERATOR> <!-- Free text --> </TRAVEL_CONTROL> </CONTROL> <!-- Header section, mandatory --> <HEADER> <!-- Invoice number (unique identifier in payee's system), mandatory --> <INVOICE_ID/> <!-- Invoice processing type identifier: 00 = normal invoice --> <PROCESS_CODE/> <!-- Invoice type code: 00 = sales invoice, 01 = credit note, 02 = collecting invoice, 03 = transit invoice, 04 = credit invoice, 05 = credit of transit invoice, 06 = interest invoice, 07 = credit of interest invoice, 08 = advance notice, 09 = request for payment, 20 = vehicle invoice, 50 = order, 51= order confirmation, 60 = purchase credit invoice, 90 = travel plan, 91= travel invoice, 99 = test invoice. Optional attribute EXTENSION, that has value 00 for non taxated external invoice. Optional attribute CODE offer possibility to specify invoice type if needed. --> <INVOICE_TYPE EXTENSION="" CODE=""/> <!-- Invoice method of charge: 00 = normal, 01 = direct debit --> <METHOD_OF_CHARGE/> <!-- Invoice delivery method: 01 = printing of sales invoice --> <METHOD_OF_INTERCHANGE/> <!-- Invoice status information --> <INVOICE_STATUS STATUS_CODE=""/> <!-- Descriptive header for the invoice --> <SUBJECT/> <!-- Credit note number --> <CREDIT_INVOICE_NUMBER/> <!-- Credit note date --> <CREDIT_INVOICE_DATE> </CREDIT_INVOICE_DATE> <!-- Credit note due date --> <CREDIT_INVOICE_DUE_DATE> </CREDIT_INVOICE_DUE_DATE> <!-- Invoice date, mandatory --> <INVOICE_DATE> </INVOICE_DATE> <!-- Invoice due date --> <DUE_DATE> 8(45)
9 <!-- Alternatives: DATE or VERBOSE_DATE, including for e.g text "Immediately!" --> <VERBOSE_DATE/> </DUE_DATE> <!-- Time to reclaim --> <REMARK_TIME/> <!-- Next due date or due dates --> <NEXT_DUE_DATE> </NEXT_DUE_DATE> <!-- Invoice value date --> <VALUE_DATE> </VALUE_DATE> <!-- Period start date --> <START_PERIOD> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> <!-- Alternatively invoicing period in text mode --> <PERIOD_TEXT/> </START_PERIOD> <!-- Actual delivery date --> <DELIVERY_DATE> </DELIVERY_DATE> <!-- Terms of delivery information --> <TERMS_OF_DELIVERY TERMS_OF_DELIVERY_CODE=""/> <!-- Period end date --> <END_PERIOD> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> 9(45)
10 </END_PERIOD> <!-- Note number --> <NOTE_NUMBER/> <!-- Terms of payment --> <!-- Optional attribute TERMS_OF_PAYMENT_CODE for terms of payment code --> <TERMS_OF_PAYMENT TERMS_OF_PAYMENT_CODE=""/> <!-- Cash discount --> <CASH_DISCOUNT> <!-- Cash date --> <!-- Cash discount-% --> <PER_CENT/> <!-- Cash discount amount, mandatory VAT -attribute --> <CASH_DISCOUNT_AMOUNT> </CASH_DISCOUNT_AMOUNT> <!-- Cash discount tax amount in applied tax bases --> <VAT> <!-- Tax-% --> <RATE/> <!-- Tax amount --> <VAT_AMOUNT> </VAT_AMOUNT> <!-- Free text --> </VAT> <!-- Tax amount for the sum including cash discount --> <VAT_TOTAL> </VAT_TOTAL> <!-- Invoice total sum including cash discount, mandatory VAT -attribute --> <INVOICE_TOTAL_WITH_CASH_DISCOUNT> </INVOICE_TOTAL_WITH_CASH_DISCOUNT> <!-- Cash discount text --> </CASH_DISCOUNT> <!-- Overdue interest or fine --> <PAYMENT_OVERDUE_FINE> <!-- Overdue interest-% --> <INTEREST_RATE/> <!-- Extra charge --> <SURCHARGE> </SURCHARGE> <!-- Interest, free text --> </PAYMENT_OVERDUE_FINE> <!-- Currency information --> <CURRENCY> <!-- Currency code --> <CODE/> <!-- Currency rate --> <RATE/> <!-- Date for the Currency rate --> 10(45)
11 </CURRENCY> <!-- Trade code --> <EU_TRADE_CODE/> <!-- Subject of payment code (According Finnish Bankers Association coding): 70 = rent, 71 = electricity, 72 = water, 73 = telephone, 74 = insurance, 75 = medical doctor, 76 = hospital, 77 = school, 78 = newspaper, 79 = subscription, 80 = tax, 81 = VAT, 82 = employee payment, 83 = license (authorities), 84 = instalment, 85 = factoring, 86 = credit card and instalment, 89 = invoice, 90 = other --> <PAYMENT_SUBJECT_CODE/> <!-- Payment subject identifier --> <PAYMENT_INSTRUCTION_IDENTIFIER/> <!-- Reference given by orderer, preferrebly use ORDER_INFORMATION -structure --> <ORDER_REFERENCE/> <!-- Invoice handler --> <CONTROLLER/> <!-- Order information --> <!-- Attribute ORDER_TYPE defines order party. More information in TEAPPSXML Implementation Guide --> <ORDER_INFORMATION ORDER_TYPE=""> <!-- Order number --> <ORDER_NUMBER/> <!-- Order date --> <ORDER_DATE> </ORDER_DATE> <!-- Order reference --> <ORDER_REFERENCE/> <!-- Order position --> <ORDER_POSITION/> </ORDER_INFORMATION> <!-- Order confirmation information --> <ORDER_CONFIRMATION> <!-- Order confirmation number --> <ORDER_CONFIRMATION_NUMBER/> <!-- Order confirmation date --> <ORDER_CONFIRMATION_DATE> </ORDER_CONFIRMATION_DATE> </ORDER_CONFIRMATION> <!-- Contract information --> <CONTRACT_INFORMATION CONTRACT_CODE="" CONTRACT_TYPE=""> <!-- Contract number --> <CONTRACT_NUMBER/> <!-- Contract date --> <CONTRACT_DATE> </CONTRACT_DATE> 11(45)
12 <!-- Contract period --> <CONTRACT_PERIOD> <!-- Period start date --> <START_PERIOD> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> <!-- Alternatively period data in text mode --> <PERIOD_TEXT/> </START_PERIOD> <!-- Period end date --> <END_PERIOD> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> </END_PERIOD> </CONTRACT_PERIOD> <!-- Pricelist --> <PRICELIST/> </CONTRACT_INFORMATION> <!-- Project information --> <PROJECT_INFORMATION PROJECT_TYPE=""> <!-- Project number or identifier --> <PROJECT_NUMBER/> <!-- Project name --> <PROJECT_TITLE/> <!-- Free text --> </PROJECT_INFORMATION> <!-- Transportation information --> <!-- Optional attribute TRANSPORT_ID that identifies main and forward transportations --> <TRANSPORT_INFORMATION TRANSPORT_ID=""> <!-- Mode of transport --> <!-- Optional attribute MODE_OF_TRANSPORT_ID, transport mode code --> <MODE_OF_TRANSPORT MODE_OF_TRANSPORT_ID=""/> <!-- Vehicle information --> <CARRIER> <!-- Transportation company --> <CARRIER_NAME/> <!-- Vehicle identifier --> <VESSEL/> </CARRIER> <!-- Transportation location information --> <!-- Optional attribute LOCATION_ID, further specifying code --> <LOCATION LOCATION_ID=""/> <!-- Transportation related date --> 12(45)
13 <!-- Country of origin --> <COUNTRY_OF_ORIGIN> <!-- Country code --> <COUNTRY_CODE/> <!-- Country --> <COUNTRY/> </COUNTRY_OF_ORIGIN> <!-- Destination country --> <COUNTRY_OF_DESTINATION> <!-- Country code --> <COUNTRY_CODE/> <!-- Country --> <COUNTRY/> </COUNTRY_OF_DESTINATION> <!-- Discharge location --> <PLACE_OF_DISCHARGE/> <!-- Final destination location --> <FINAL_DESTINATION/> <!-- Transportation reference eg. waybill number --> <TRANSPORT_NOTE TRANSPORT_NOTE_TYPE=""/> </TRANSPORT_INFORMATION> <!-- Packing marks --> <PACKING_MARKS> <!-- Packing mark --> <PACKING_MARK/> <!-- Description of packing mark --> <PACKING_DESCRIPTION/> <!-- Customs tariff list number --> <CN_NAME/> <!-- Box number --> <PACK_QUANTITY Q_UNIT="" SIGN=""/> <!-- Gross weight --> <GROSS_WEIGHT Q_UNIT="" SIGN=""/> <!-- Net weight --> <NET_WEIGHT Q_UNIT="" SIGN=""/> <!-- Measures --> <MEASUREMENTS> <!-- Length --> <LENGTH Q_UNIT="" SIGN=""/> <!-- Width --> <WIDTH Q_UNIT="" SIGN=""/> <!-- Height --> <HEIGHT Q_UNIT="" SIGN=""/> </MEASUREMENTS> <!-- Measures as text string, alternative for MEASUREMENTS -structure --> <MEASUREMENT_TEXT/> <!-- Volume --> <VOLUME Q_UNIT="" SIGN=""/> </PACKING_MARKS> <!-- Packing marks altogether --> <TOTAL_PACKING_MARKS> <!-- Box number --> <TOTAL_PACK_QUANTITY Q_UNIT="" SIGN=""/> <!-- Gross weight --> <TOTAL_GROSS_WEIGHT Q_UNIT="" SIGN=""/> <!-- Net weight --> <TOTAL_NET_WEIGHT Q_UNIT="" SIGN=""/> 13(45)
14 <!-- Measures --> <TOTAL_MEASUREMENTS> <!-- Length --> <LENGTH Q_UNIT="" SIGN=""/> <!-- Width --> <WIDTH Q_UNIT="" SIGN=""/> <!-- Height --> <HEIGHT Q_UNIT="" SIGN=""/> </TOTAL_MEASUREMENTS> <!-- Measures as text string, alternative for TOTAL_MEASUREMENTS -structure --> <TOTAL_MEASUREMENT_TEXT/> <!-- Volume --> <TOTAL_VOLUME Q_UNIT="" SIGN=""/> </TOTAL_PACKING_MARKS> <!-- Credit card invoice information --> <CREDIT_INFORMATION> <!-- Credit limit --> <CREDIT_LIMIT> </CREDIT_LIMIT> <!-- Interest --> <INTEREST> <PER_CENT/> </INTEREST> <!-- Available limit --> <OPERATION_LIMIT> </OPERATION_LIMIT> <!-- Monthly instalment --> <INSTALMENT> </INSTALMENT> </CREDIT_INFORMATION> <!-- Factoring invoice information --> <FACTORING_INFORMATION> <!-- Factoring agreement number --> <AGREEMENT_NUMBER/> <!-- Transition list number --> <TRANSMISSION_LIST_NUMBER/> <!-- Type of endorsement clause --> <ENDORSEMENT_CLAUSE/> <!-- Factoring type code --> <FACTORING_TYPE/> <!-- Name of the Factoring company --> <CUSTOMER_NAME/> <!-- Organisation code of factoring code --> <ORGANIZATION_NUMBER/> <!-- Other identifier for the Factoring company --> <ID/> <!-- Free text --> </FACTORING_INFORMATION> <!-- Default posting --> <PAYER_POSTING_DEFAULTS> <!-- Debit account --> <CHARGE_ACCOUNT/> <!-- Expense account --> <CREDIT_ACCOUNT/> <!-- Basic account list; short account number --> <SHORT_ACCOUNT_ID/> <!-- Basic account list; normal account number --> <NORMAL_ACCOUNT_ID/> 14(45)
15 <!-- Bookkeeping dimensions --> <DIMENSIONS> <DIMENSION> <LEVEL TITLE=""/> <DIMENSION_VALUE DIMENSION_LENGTH=""/> <DIMENSION_NAME/> </DIMENSION> </DIMENSIONS> </PAYER_POSTING_DEFAULTS> <!-- Grouping of default posting --> <PAYER_POSTING_GROUP_DEFAULTS> <POSTING_DEFAULT> <!-- Expense account, optional attribute TITLE --> <ACCOUNT TITLE=""/> <!-- Management account, optional attribute TITLE --> <ACCOUNT_2 TITLE=""/> <!-- Booked monetary amount, mandatory VAT-attribute --> <ACCOUNT_AMOUNT> </ACCOUNT_AMOUNT> <!-- Basic account list, short account number --> <SHORT_ACCOUNT_ID/> <!-- Basic account list, normal account number --> <NORMAL_ACCOUNT_ID/> <!-- Bookkeeping dimensions --> <DIMENSIONS> <DIMENSION> <LEVEL TITLE=""/> <DIMENSION_VALUE DIMENSION_LENGTH=""/> <DIMENSION_NAME/> </DIMENSION> </DIMENSIONS> <!-- Accounting reference --> <ACCOUNT_REFERENCE/> <!-- Reporting code --> <REPORTING_CODE/> <!-- Control stamp --> <CONTROL_STAMP> <CONTROL_DATE> </CONTROL_DATE> <CONTROL_USER/> </CONTROL_STAMP> <!-- Acceptance stamp --> <ACCEPTANCE_STAMP> <ACCEPTANCE_DATE> </ACCEPTANCE_DATE> <ACCEPT_USER/> </ACCEPTANCE_STAMP> </POSTING_DEFAULT> </PAYER_POSTING_GROUP_DEFAULTS> <!-- Seller accounting instruction --> <SELLER_ACCOUNT_TEXT/> 15(45)
16 <!-- Order number related with invoice, preferrebly use ORDER_INFORMATION -structure --> <INVOICE_ORDER_NUMBER/> <!-- Buyer reference --> <BUYER_REFERENCE/> <!-- Deliverer reference --> <DELIVERER_REFERENCE/> <!-- Home clearance permission --> <CLEARANCE_NUMBER/> <!-- VAT text --> <VAT_TEXT/> <!-- Invoice subject additional information --> <HEADER_INFO> <!-- Serial number, code which denotes order. Format 01, 02, 03 etc. --> <SERIAL_ID/> <!-- Header, INFO_TYPE-attribute includes header code value, more information in TEAPPSXML Implementation Guide --> <TITLE INFO_TYPE=""/> <!-- Contents --> <CONTENT Q_UNIT="" SIGN=""/> </HEADER_INFO> <!-- Link, optional attributes TYPE and OBJECT --> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> <!-- Presentment service information --> <INVOICE_APPENDIX_SERVICE> <!-- Link --> <LINK TYPE="" OBJECT=""/> <!-- Identifier --> <APPENDIX_ID/> </INVOICE_APPENDIX_SERVICE> <!-- Free text --> <!-- Optional attribute TEXT_TYPE, code for text content --> </HEADER> <!-- Direct debit, optional --> <DIRECTCHARGE> <!-- Batch information --> <BANK_BATCH> <!-- Payee service number (Bankers Association identifier) --> <PAYEE_SERVICE_CODE/> <!-- Bank group identifier --> <BANK_CODE/> <!-- Currency id-code: 0 = mk, 1 = euro --> <CURRENCY_ID/> <!-- Reserved --> <INRESERVE/> </BANK_BATCH> <!-- Charge request information --> <BANK_CHARGE> <!-- Record identifier: 2 = einvoice, 3 = direct debit --> <RECORD_TYPE/> <!-- Transaction type code: 50 = charge request, 54 = einvoice, 55 = charge, 56 = credit, 52 = direct payment --> <TRANSACTION_TYPE_CODE/> <!-- Due date --> <BANK_DUE_DATE> 16(45)
17 </BANK_DUE_DATE> <!-- Processing identifier: 0 = charge, 1 = cancellation, 2 = credit --> <PROCESSING_CODE/> <!-- Payee account number --> <PAYER_ACCOUNT_NUMBER/> <!-- Monetary amount --> <TOTAL> </TOTAL> <!-- Payment subject --> <PAYMENT_SUBJECT_CODE/> <!-- Payee account number --> <PAYEE_ACCOUNT_NUMBER/> <!-- Payer name --> <PAYER_CUSTOMER_NAME/> <!-- Payment reference --> <DETAILS_OF_PAYMENT MESSAGE_TYPE=""> <!-- Finnish payment reference, international payment reference or free text --> <FI_PAYMENT_REFERENCE/> <IPI_REFERENCE/> <FREE_TEXT/> </DETAILS_OF_PAYMENT> <!-- Message --> <MESSAGE/> </BANK_CHARGE> </DIRECTCHARGE> <!-- Invoice sender, for e.g. account office working on behalf of the customer --> <INVOICE_SENDER> <!-- Company name information --> <CUSTOMER_INFORMATION> <!-- Company name, mandatory --> <CUSTOMER_NAME/> <!-- Customer number --> <CUSTOMER_ID/> <!-- Address information --> <ADDRESS> <!-- Street address/post Box --> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <!-- ZIP code --> <POSTAL_CODE/> <!-- City --> <POST_OFFICE/> <!-- Country --> <COUNTRY/> <!-- Country code --> <COUNTRY_CODE/> </ADDRESS> <!-- VAT-registering information --> <VAT_REG/> <!-- VAT-register number --> <VAT_NUMBER/> <!-- Social security code --> <SOCIAL_SECURITY_NUMBER/> <!-- Organisation number --> <ORGANIZATION_NUMBER/> <!-- OVT-code or other company identifier, optional attribute AUTHORITY further identification for id--> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <!-- Trade register number --> <TRADE_REGISTRY_NUMBER/> <!-- Site, location --> <SITE/> 17(45)
18 <!-- Department --> <ORGANIZATION_DEPARTMENT/> <!-- Contact person --> <CONTACT_INFORMATION> <!-- Contact person name --> <CONTACT_PERSON/> <!-- Title/position --> <CONTACT_PERSON_FUNCTION/> <!-- Telephone number --> <TELEPHONE_NUMBER/> <!-- Fax-number --> <TELEFAX_NUMBER/> <!-- -address --> <!-- Free text --> </CONTACT_INFORMATION> <EU-COUNTRY> <!-- EU-country name --> <EU_COUNTRY_NAME/> <!-- EU-country code --> <EU_COUNTRY_CODE/> </EU-COUNTRY> <!-- Language code --> <LANGUAGE_CODE/> <!-- -address --> <!-- Reference --> <NOTE/> <!-- Link, optional attributes TYPE and OBJECT --> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> <!-- Free text --> <!-- Optional attribute TEXT_TYPE, code specifier for contents --> </CUSTOMER_INFORMATION> </INVOICE_SENDER> <!-- Payee, mandatory --> <PAYEE> <!-- Company information --> <CUSTOMER_INFORMATION> <!-- Company name, mandatory --> <CUSTOMER_NAME/> <!-- Supplier number --> <CUSTOMER_ID/> <!-- Address information. PAYEE/CUSTOMER_INFORMATION/ADDRESS -structure will consist Company official address. --> <ADDRESS> <!-- Street address/po Box --> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <!-- Zip code --> <POSTAL_CODE/> <!-- City --> <POST_OFFICE/> <!-- Country --> <COUNTRY/> <!-- Country code --> <COUNTRY_CODE/> </ADDRESS> 18(45)
19 <!-- VAT registration information --> <VAT_REG/> <!-- VAT register number --> <VAT_NUMBER/> <!-- Social security code --> <SOCIAL_SECURITY_NUMBER/> <!-- Organisation number --> <ORGANIZATION_NUMBER/> <!-- OVT-code or other company identifier, optional attribute AUTHORITY further identification for id--> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <!-- Trade registry number --> <TRADE_REGISTRY_NUMBER/> <!-- Site, location --> <SITE/> <!-- Department --> <ORGANIZATION_DEPARTMENT/> <!-- Contact person --> <CONTACT_INFORMATION> <!-- Contact person name --> <CONTACT_PERSON/> <!-- Title/position --> <CONTACT_PERSON_FUNCTION/> <!-- Telephone number --> <TELEPHONE_NUMBER/> <!-- Fax-number --> <TELEFAX_NUMBER/> <!-- -address --> <!-- Free text --> </CONTACT_INFORMATION> <EU-COUNTRY> <!-- EU-country name --> <EU_COUNTRY_NAME/> <!-- EU-country --> <EU_COUNTRY_CODE/> </EU-COUNTRY> <!-- Language code --> <LANGUAGE_CODE/> <!-- -address --> <!-- Reference --> <NOTE/> <!-- Link, optional attributes TYPE and OBJECT --> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> <!-- Free text --> <!-- Optional attribute TEXT_TYPE, code specifier for content --> </CUSTOMER_INFORMATION> <!-- Bank information --> <BANKS> <!-- Bank identifier --> <BANK_CODE/> <!-- Bank name, mandatory --> <BANK_NAME/> <!-- Bank address --> <BANK_ADDRESS/> <!-- Account number, mandatory --> <BANK_ACCOUNT_NUMBER/> <!-- Bank international name --> <SWIFT_CODE/> 19(45)
20 <!-- Account owner, international name --> <IN_FAVOR/> <!-- International account number (IBAN format) --> <IBAN_ACCOUNT_NUMBER/> <!-- Payment instruction --> <FOREIGN_PAYMENT_METHODS/> <!-- Clearing code --> <CLEARING_CODE/> </BANKS> <!-- Payee's Net Service identifier --> <NET_SERVICE_ID/> <!-- Payee's service provider --> <INTERMEDIATOR/> <!-- Payee's domicile --> <DOMICILE/> <!-- Information for premilinary tax-registration --> <PRELIMINARY_TAX_REGISTERED/> <!-- Archiving identifier --> <ARCHIVE_ID/> <!-- Netting code --> <NETTING_CODE/> <!-- Payee's reference --> <PAYEE_REFERENCE/> <!-- Payment method, optional attribute CODE --> <METHOD_OF_PAYMENT CODE=""/> <!-- Payment reference --> <DETAILS_OF_PAYMENT MESSAGE_TYPE=""> <!-- Finnish payment reference, international payment reference or free text --> <FI_PAYMENT_REFERENCE/> <IPI_REFERENCE/> <FREE_TEXT/> </DETAILS_OF_PAYMENT> <!-- Bank barcode --> <BANK_BARCODE> <!-- Finnish or international barcode --> <FI_BANK_BARCODE/> <!-- Alternatives:FI_BANK_BARCODE or IPI_BANK_BARCODE --> </BANK_BARCODE> </PAYEE> <!-- Seller/seller organisation information, optional --> <SALES_CONTACT> <CUSTOMER_INFORMATION> <CUSTOMER_NAME/> <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> 20(45)
21 <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> </SALES_CONTACT> <!-- Invoice real receiver, for e.g accounting office working on behalf of the customer, informative data --> <INVOICE_RECIPIENT> <!-- Company information --> <CUSTOMER_INFORMATION> <!-- Company name, mandatory --> <CUSTOMER_NAME/> <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> 21(45)
22 </INVOICE_RECIPIENT> <!-- Receiver information, mandatory --> <RECEIVER> <!-- Company information --> <CUSTOMER_INFORMATION> <!-- Company name, mandatory --> <CUSTOMER_NAME/> <!-- Customer number --> <CUSTOMER_ID/> <ADDRESS> <!-- Street address/po Box --> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <!-- Zip code --> <POSTAL_CODE/> <!-- City --> <POST_OFFICE/> <!-- Country --> <COUNTRY/> <!-- Country code --> <COUNTRY_CODE/> </ADDRESS> <!-- VAT registration information --> <VAT_REG/> <!-- VAT register number --> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <!-- Organisation number --> <ORGANIZATION_NUMBER/> <!-- OVT-code or other company identifier, optional attribute AUTHORITY further identification for id--> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <!-- Trade registry number --> <TRADE_REGISTRY_NUMBER/> <!-- Site, location --> <SITE/> <!-- Department --> <ORGANIZATION_DEPARTMENT/> <!-- Contact person --> <CONTACT_INFORMATION> <!-- Contact person name --> <CONTACT_PERSON/> <!-- Title/position --> <CONTACT_PERSON_FUNCTION/> <!-- Telephone number --> <TELEPHONE_NUMBER/> <!-- Fax-number --> <TELEFAX_NUMBER/> <!-- -address --> <!-- Free text --> </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <!-- Language code --> <LANGUAGE_CODE/> <!-- -address --> <!-- Reference --> <NOTE/> 22(45)
23 <!-- Link, optional attributes TYPE and OBJECT --> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> <!-- Free text --> <!-- Optional attribute TEXT_TYPE, code specifier for content --> </CUSTOMER_INFORMATION> <!-- Customer number, preferrebly use CUSTOMER_INFORMATION/CUSTOMER_ID -element --> <CUSTOMER_ID/> <!-- Receiver's Net Service identifier --> <NET_SERVICE_ID/> <!-- Receiver's Service provider --> <INTERMEDIATOR/> <!-- Archiving identifier --> <ARCHIVE_ID/> <!-- Netting code --> <NETTING_CODE/> <!-- Customer segment --> <CUSTOMER_SEGMENT/> <!-- Receiver's -address if invoice will be delivered by ; agreed in service installation --> <MAIL_ID/> <!-- Printing control --> <PRINTING> <!-- Cover page template identifier --> <FORM_FIRST_PAGE/> <!-- Continuation page template identifier --> <FORM_CONT_PAGE/> <!-- Specification page template identifier --> <FORM_SPEC_PAGE/> <!-- Number of copies --> <COPIES/> </PRINTING> </RECEIVER> <!-- Deliverer information, optional --> <DELIVERER> <!-- Company information --> <CUSTOMER_INFORMATION> <CUSTOMER_NAME/> <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> 23(45)
24 </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> </DELIVERER> <!-- Orderer information, optional --> <ORDERER> <!-- Company information --> <CUSTOMER_INFORMATION> <CUSTOMER_NAME/> <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> </ORDERER> 24(45)
25 <!-- Delivery party information, optional --> <DELIVERY_PARTY> <!-- Company information --> <CUSTOMER_INFORMATION> <CUSTOMER_NAME/> <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> </DELIVERY_PARTY> <!-- Payer information, optional --> <PAYER> <!-- Company information --> <CUSTOMER_INFORMATION> <CUSTOMER_NAME/> <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> 25(45)
26 <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> <!-- Payer's Net Service identifier --> <NET_SERVICE_ID/> <!-- Payer's Service provider --> <INTERMEDIATOR/> <!-- Archiving information --> <ARCHIVE_ID/> </PAYER> <!-- Payor information, optional --> <PAYOR> <!-- Company information --> <CUSTOMER_INFORMATION> <CUSTOMER_NAME/> <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> 26(45)
27 </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> </PAYOR> <!-- Manufacturer information, optional --> <MANUFACTURER> <!-- Company information --> <CUSTOMER_INFORMATION> <CUSTOMER_NAME/> <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> </MANUFACTURER> <!-- Holder information, optional --> <HOLDER> <!-- Company information --> <CUSTOMER_INFORMATION> <CUSTOMER_NAME/> 27(45)
28 <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> </HOLDER> <!-- Other party for the invoice, optional. This can be used if no suitable party information available. --> <!-- In mandatory PARTNER_TYPE and PARTNER_TEXT-attribute one has to identify party details. More information in TEAPPSXML Implementation Guide --> <OTHER_PARTNER PARTNER_TYPE="" PARTNER_TEXT=""> <!-- Company information --> <CUSTOMER_INFORMATION> <CUSTOMER_NAME/> <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> 28(45)
29 <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> </OTHER_PARTNER> <!-- Invoice rows, optional --> <ROWS> <!-- ROW_TYPE - row type: MAIN = header row, SPECIFICATION = specification row, SUBTOTAL = sub-total row, INFO = additional information row. ROW_ID is used for row numbering. More information in TEAPPSXML Implementation Guide --> <ROW ROW_TYPE="" ROW_ID=""> <!-- Row number --> <ROW_NUMBER/> <!-- Delivery receiving customer, optional --> <DELIVERY_RECEIVER> <CUSTOMER_INFORMATION> <CUSTOMER_NAME/> <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> 29(45)
30 <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> </DELIVERY_RECEIVER> <!-- Other party for the row, optional. This can be used if no suitable party information available. --> <!-- In mandatory PARTNER_TYPE and PARTNER_TEXT-attribute one has to identify party details. More information in TEAPPSXML Implementation Guide --> <OTHER_PARTNER PARTNER_TYPE="" PARTNER_TEXT=""> <!-- Company information --> <CUSTOMER_INFORMATION> <CUSTOMER_NAME/> <CUSTOMER_ID/> <ADDRESS> <STREET_ADDRESS1/> <STREET_ADDRESS2/> <STREET_ADDRESS3/> <STREET_ADDRESS4/> <POSTAL_CODE/> <POST_OFFICE/> <COUNTRY/> <COUNTRY_CODE/> </ADDRESS> <VAT_REG/> <VAT_NUMBER/> <SOCIAL_SECURITY_NUMBER/> <ORGANIZATION_NUMBER/> <PARTY_IDENTIFICATION_ID AUTHORITY=""/> <TRADE_REGISTRY_NUMBER/> <SITE/> <ORGANIZATION_DEPARTMENT/> <CONTACT_INFORMATION> <CONTACT_PERSON/> <CONTACT_PERSON_FUNCTION/> <TELEPHONE_NUMBER/> <TELEFAX_NUMBER/> </CONTACT_INFORMATION> <EU-COUNTRY> <EU_COUNTRY_NAME/> <EU_COUNTRY_CODE/> </EU-COUNTRY> <LANGUAGE_CODE/> <NOTE/> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> </CUSTOMER_INFORMATION> </OTHER_PARTNER> <!-- Article information --> <ARTICLE> <!-- Product identifier --> <!-- Optional attribute ARTICLE_CODE, further specification for product identifier --> <ARTICLE_ID ARTICLE_CODE=""/> 30(45)
31 <!-- Product name --> <ARTICLE_NAME/> <ARTICLE_NAME2/> <!-- Actual delivery date --> <DELIVERY_DATE> </DELIVERY_DATE> <!-- EAN-code --> <EAN_CODE/> <!-- Supplier's product identifier --> <SUPPLIER_ARTICLE_ID/> <!-- Manufacturer's product identifier --> <MANUFACTURER_ARTICLE_ID/> <!-- Product group --> <PRODUCT_GROUP/> <!-- Serial number --> <SERIAL_NUMBER/> <!-- Batch information --> <LOT> <!-- Batch number --> <LOT_NUMBER/> <!-- Description --> <LOT_DESCRIPTION/> </LOT> <!-- Free text --> <!-- Product properties --> <ARTICLE_DESCRIPTIONS> <ARTICLE_DESCRIPTION> <!-- Property type --> <!-- Optional attribute DESCRIPTION_ID, specifier for property type --> <DESCRIPTION_TYPE DESCRIPTION_ID=""/> <!-- Property --> <DESCRIPTION_VALUE/> <!-- Property unit --> <DESCRIPTION_UNIT/> </ARTICLE_DESCRIPTION> </ARTICLE_DESCRIPTIONS> </ARTICLE> <!-- Measures and dates --> <LOCATION_ID> <!-- Used quantity, Q_UNIT -quantity unit attribute, SIGN -attribute for plus/minus sign --> <USED_QUANTITY Q_UNIT="" SIGN=""/> <!-- Earlier measurement --> <PREVIOUS_METER_READING/> <!-- Previous reading date --> <PREVIOUS_METER_READING_DATE> </PREVIOUS_METER_READING_DATE> <!-- New metering value --> <LATEST_METER_READING/> <!-- New reading date --> <LATEST_METER_READING_DATE> 31(45)
32 </LATEST_METER_READING_DATE> <!-- Invoiced amount, Q_UNIT -attribute includes unit for amount, SIGN -attribute used for plus/minus sign --> <CALCULATED_QUANTITY Q_UNIT="" SIGN=""/> <!-- Average price --> <AVERAGE_PRICE> </AVERAGE_PRICE> </LOCATION_ID> <!-- Period start date --> <START_PERIOD> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> <!-- Alternatively period information as text string --> <PERIOD_TEXT/> </START_PERIOD> <!-- Period end date --> <END_PERIOD> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> </END_PERIOD> <!-- Quantity --> <QUANTITY> <!-- Offered amount, Q_UNIT -attribute includes unit, SIGN -attribute for plus/minus sign --> <OFFERED Q_UNIT="" SIGN=""/> <!-- Ordered amount, Q_UNIT -attribute includes unit, SIGN -attribute for plus/minus sign --> <ORDERED Q_UNIT="" SIGN=""/> <!-- Confirmed amount, Q_UNIT -attribute includes unit, SIGN -attribute for plus/minus sign --> <CONFIRMED Q_UNIT="" SIGN=""/> <!-- Delivered amount, Q_UNIT -attribute includes unit, SIGN -attribute for plus/minus sign --> <DELIVERED Q_UNIT="" SIGN=""/> <!-- Invoiced amount, Q_UNIT -attribute includes unit, SIGN -attribute for plus/minus sign --> <CHARGED Q_UNIT="" SIGN=""/> <!-- Postdelivered amount, Q_UNIT -attribute includes unit, SIGN -attribute for plus/minus sign --> <POSTDELIVERED Q_UNIT="" SIGN=""/> <!-- Amount requested for credit. Q_UNIT -attribute includes unit, SIGN -attribute for plus/minus sign --> <CREDIT_REQUESTED Q_UNIT="" SIGN=""/> <!-- Returned amount, Q_UNIT -attribute includes unit, SIGN -attribute for plus/minus sign --> <RETURNED Q_UNIT="" SIGN=""/> </QUANTITY> 32(45)
33 <!-- Sales contact --> <SALES_PERSON/> <!-- Pricelist --> <PRICELIST/> <!-- Credit invoice number --> <CREDIT_INVOICE_NUMBER/> <!-- Payee reference --> <PAYEE_REFERENCE/> <!-- Contract reference --> <CONTRACT_REFERENCE/> <!-- Offer reference --> <OFFER_REFERENCE/> <!-- Quotation reference --> <REQUEST_OF_QUOTATION_REFERENCE/> <!-- Order reference, given by orderer, preferrebly use ORDER_INFORMATION -structure --> <ORDER_REFERENCE/> <!-- Order number, preferrebly use ORDER_INFORMATION -structure --> <ORDER_NUMBER/> <!-- Order date, preferrebly use ORDER_INFORMATION -structure --> <ORDER_DATE> </ORDER_DATE> <!-- Order information --> <!-- Attribute ORDER_TYPE identifier order party. More information TEAPPSXML Implementation Guide --> <ORDER_INFORMATION ORDER_TYPE=""> <!-- Order number --> <ORDER_NUMBER/> <!-- Order date --> <ORDER_DATE> </ORDER_DATE> <!-- Order reference --> <ORDER_REFERENCE/> <!-- Order position --> <ORDER_POSITION/> </ORDER_INFORMATION> <!-- Contract information --> <CONTRACT_INFORMATION CONTRACT_CODE="" CONTRACT_TYPE=""> <!-- Contract number --> <CONTRACT_NUMBER/> <!-- Contract date --> <CONTRACT_DATE> </CONTRACT_DATE> <!-- Contract period --> <CONTRACT_PERIOD> <!-- Period start date --> <START_PERIOD> 33(45)
34 <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> <!-- Alternatively period information as text string --> <PERIOD_TEXT/> </START_PERIOD> <!-- Period end date --> <END_PERIOD> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> </END_PERIOD> </CONTRACT_PERIOD> <!-- Price list --> <PRICELIST/> </CONTRACT_INFORMATION> <!-- Project information --> <PROJECT_INFORMATION PROJECT_TYPE=""> <!-- Project number or identifier --> <PROJECT_NUMBER/> <!-- Project name --> <PROJECT_TITLE/> <!-- Free text --> </PROJECT_INFORMATION> <!-- Terms of delivery --> <TERMS_OF_DELIVERY TERMS_OF_DELIVERY_CODE=""/> <!-- Note number --> <NOTE_NUMBER/> <!-- Method of delivery --> <!-- Optional attribute DELIVERY_CODE, further identification for delivery method --> <DELIVERY_INFORMATION DELIVERY_CODE=""/> <!-- Terminal address --> <TERMINAL_ADDRESS/> <!-- Delivery number, given by payee --> <DELIVERY_NUMBER/> <!-- Transport note number --> <TRANSPORT_NOTE TRANSPORT_NOTE_TYPE=""/> <!-- Transport note date --> <TRANSPORT_DATE> </TRANSPORT_DATE> 34(45)
35 <!-- Discharge location --> <PLACE_OF_DISCHARGE/> <!-- Final destination, location --> <FINAL_DESTINATION/> <!-- Packing marks --> <PACKING_MARKS> <!-- Packing mark --> <PACKING_MARK/> <!-- Packing mark description --> <PACKING_DESCRIPTION/> <!-- Customs tariff list name --> <CN_NAME/> <!-- Number of Boxes/packings --> <PACK_QUANTITY Q_UNIT="" SIGN=""/> <!-- Gross weight --> <GROSS_WEIGHT Q_UNIT="" SIGN=""/> <!-- Net weight --> <NET_WEIGHT Q_UNIT="" SIGN=""/> <!-- Measurements --> <MEASUREMENTS> <!-- Length --> <LENGTH Q_UNIT="" SIGN=""/> <!-- Width --> <WIDTH Q_UNIT="" SIGN=""/> <!-- Height --> <HEIGHT Q_UNIT="" SIGN=""/> </MEASUREMENTS> <!-- Measures as text string, alternative for MEASUREMENTS -structure --> <MEASUREMENT_TEXT/> <!-- Volume --> <VOLUME Q_UNIT="" SIGN=""/> </PACKING_MARKS> <!-- Unit, preferrebly use element's Q_UNIT -attribute --> <UNIT/> <!-- Action --> <ROW_ACTION/> <!-- Currency information in row if different from Invoice currency --> <CURRENCY> <!-- Currency code --> <CODE/> <!-- Currency rate --> <RATE/> <!-- Currency rate date --> </CURRENCY> <!-- Unit price for product, VAT -attribute, mandatory, PR_UNIT - attribute for pricing unit --> <PRICE_PER_UNIT PR_UNIT=""> </PRICE_PER_UNIT> <!-- Discount/Unit-price, VAT -attribute, mandatory --> <DISCOUNT_FROM_PRICE_PER_UNIT> </DISCOUNT_FROM_PRICE_PER_UNIT> <!-- Discounted unit-price, VAT -attribute mandatory --> <PRICE_PER_UNIT_WITH_DISCOUNT> </PRICE_PER_UNIT_WITH_DISCOUNT> 35(45)
36 <!-- Unit price including discounts and extras, VAT -attribute mandatory --> <PRICE_PER_UNIT_NET> </PRICE_PER_UNIT_NET> <!-- Wholesale price, VAT -attribute mandatory --> <WHOLESALE_PRICE> </WHOLESALE_PRICE> <!-- List price, VAT -attribute mandatory --> <LIST_PRICE> </LIST_PRICE> <!-- Row discount for product --> <!-- Type of discount in TYPE-attribute: 00/empty = normal, 01 = cash discount, 02 = contract discount --> <DISCOUNT TYPE=""> <!-- Discount description --> <DISCOUNT_NAME/> <!-- Discount-% --> <PER_CENT/> <!-- Row discount total, VAT -attribute mandatory --> <DISCOUNT_AMOUNT> </DISCOUNT_AMOUNT> </DISCOUNT> <!-- Row level extra or other allowance than discount--> <ROW_CHARGE> <!-- Description --> <CHARGE_NAME/> <!-- Per cent --> <PER_CENT/> <!-- From total, VAT -attribute mandatory --> <CHARGE_FROM_AMOUNT> </CHARGE_FROM_AMOUNT> <!-- Total, VAT -attribute mandatory --> <CHARGE_AMOUNT> </CHARGE_AMOUNT> </ROW_CHARGE> <!-- Payable sum, net sum (unit price * amount - discounts/allowances + charges), VAT -attribute mandatory --> <ROW_TOTAL> </ROW_TOTAL> <!-- Net sum in other currency, VAT -attribute mandatory --> <ROW_TOTAL_IN_OTHER_CURRENCY> <CURRENCY> <CODE/> <RATE/> </CURRENCY> </ROW_TOTAL_IN_OTHER_CURRENCY> <!-- Gross sum (unit price * amount), VAT -attribute mandatory --> <ROW_AMOUNT> </ROW_AMOUNT> 36(45)
37 <!-- Row sum after discounts before extras, VAT -attribute mandatory --> <ROW_TOTAL_WITHOUT_EXTRA_COSTS> </ROW_TOTAL_WITHOUT_EXTRA_COSTS> <!-- Row VAT, optional attribute VAT_TYPE identifier for tax type --> <VAT VAT_TYPE=""> <!-- Row VAT-% --> <RATE/> <!-- Row VAT-sum --> <VAT_AMOUNT> </VAT_AMOUNT> <!-- Row VAT, Free text --> </VAT> <!-- Row level insurance information --> <INSURANCE> <!-- Insurance-% --> <PER_CENT/> <!-- Insurance from sum, VAT -attribute mandatory --> <FROM_AMOUNT> </FROM_AMOUNT> <!-- Insurance sum, VAT -attribute mandatory --> <INSURANCE_AMOUNT> </INSURANCE_AMOUNT> </INSURANCE> <!-- Information costs, VAT -attribute mandatory --> <INFO_COSTS> </INFO_COSTS> <!-- Row currency information --> <CURRENCY_INFORMATION> <!-- Currency term explanation --> <TERM_EXPLANATION/> <!-- Original unit price, VAT -attribute mandatory --> <FIXED_PRICE_PER_UNIT> </FIXED_PRICE_PER_UNIT> <!-- Agreed rate --> <FIXED_EXCHANGE_RATE/> <!-- Rate at billing time --> <INVOICE_DATE_RATE/> <!-- Currency code for term --> <CURRENCY_CODE/> <!-- Currency term variance-% --> <VARIANCE_PER_CENT/> <!-- Currency term binding-% --> <TERM_LINKAGE_PER_CENT/> </CURRENCY_INFORMATION> <!-- Product CN-data --> <CN> <!-- CN-item --> <CN_CODE/> <!-- CN-name --> <CN_NAME/> <!-- CN-item weight --> <CN_WEIGHT Q_UNIT="" SIGN=""/> <!-- CN, transportation method, text --> <CN_TRANSPORT_TEXT/> <!-- CN, origin country, code --> <COUNTRY_OF_ORIGIN_CODE/> 37(45)
38 <!-- CN, origin country, name --> <COUNTRY_OF_ORIGIN_NAME/> <!-- CN, destination country code --> <COUNTRY_OF_DESTINATION_CODE/> <!-- CN, destination country name --> <COUNTRY_OF_DESTINATION_NAME/> <!-- CN, transport method --> <MODE_OF_TRANSPORT_CODE/> <!-- CN, transaction type --> <NATURE_OF_TRANSACTION_CODE/> </CN> <!-- External product code --> <RECEIVER_PRODUCT_CODE/> <!-- Request for payment/overdue invoice row information --> <INFORMATION_OF_OVERDUE_PAYMENTS> <!-- Invoice number for original invoice --> <ORIGINAL_INVOICE_ID/> <!-- Batch number --> <PART_ID/> <!-- Date for the original invoice --> <ORIGINAL_INVOICE_DATE> </ORIGINAL_INVOICE_DATE> <!-- Due date for original invoice --> <ORIGINAL_DUE_DATE> </ORIGINAL_DUE_DATE> <!-- Original invoice total sum, VAT -attribute mandatory --> <ORIGINAL_INVOICE_TOTAL> </ORIGINAL_INVOICE_TOTAL> <!-- Original invoice payment reference --> <ORIGINAL_PAYMENT_REFERENCE/> <!-- Payment sum, VAT -attribute mandatory --> <PAID_AMOUNT> </PAID_AMOUNT> <!-- Sum not yet paid, VAT -attribute mandatory --> <UNPAID> </UNPAID> <!-- Payment date --> <DATE_OF_PAYMENT> </DATE_OF_PAYMENT> <!-- Collection date --> <COLLECTION_DATE> 38(45)
39 </COLLECTION_DATE> <!-- Collection time --> <COLLECTION_TIMES/> <!-- Collection charge, VAT -attribute mandatory --> <COLLECTION_SURCHARGE_TOTAL> </COLLECTION_SURCHARGE_TOTAL> <!-- Interest rate --> <INTEREST_RATE/> <!-- Interest period --> <INTEREST_PERIOD> <START_PERIOD> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> <PERIOD_TEXT/> </START_PERIOD> <END_PERIOD> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> </END_PERIOD> </INTEREST_PERIOD> <!-- Interest day --> <NUMBER_OF_INTEREST_DAY/> <!-- Interest amount, VAT -attribute mandatory --> <INTEREST_CHARGE> </INTEREST_CHARGE> <!-- Reference --> <REFERENCE/> <!-- Currency (if different from invoice sum currency) --> <CURRENCY> <CODE/> <RATE/> </CURRENCY> </INFORMATION_OF_OVERDUE_PAYMENTS> 39(45)
40 <!-- Row level posting --> <DEFAULT_ROW_POSTING> <!-- Credit account --> <CREDIT_ACCOUNT/> <!-- Management accounting account number --> <CREDIT_ACCOUNT_2/> <!-- Basic Account list, short account number --> <SHORT_ACCOUNT_ID/> <!-- Basic Account list, normal account number --> <NORMAL_ACCOUNT_ID/> <!-- Accounting dimensions --> <DIMENSIONS> <DIMENSION> <LEVEL TITLE=""/> <DIMENSION_VALUE DIMENSION_LENGTH=""/> <DIMENSION_NAME/> </DIMENSION> </DIMENSIONS> <!-- Account reference --> <ACCOUNT_REFERENCE/> <!-- Reporting code --> <REPORTING_CODE/> </DEFAULT_ROW_POSTING> <!-- Seller accounting instruction --> <SELLER_ACCOUNT_TEXT/> <!-- Link, optional attribute TYPE and OBJECT --> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> <!-- Link identifier --> <LINK_ID/> <!-- Arrival batch information --> <ARRIVAL_INFO> <!-- Arrival batch identifier --> <ARRIVAL_ID/> <!-- Arrival date --> <ARRIVAL_DATE> </ARRIVAL_DATE> <!-- Arrived amount --> <ARRIVED Q_UNIT="" SIGN=""/> <!-- Receipt identifier --> <RECEIPT_ID/> <!-- Delivery note identifier (supplier given) --> <DELIVERY_NOTE/> <!-- Supplier product name --> <SUPPLIER_ARTICLE_NAME/> <!-- Delivery completed --> <DELIVERY_COMPLETED/> <!-- Free text --> </ARRIVAL_INFO> <!-- Control stamp --> <CONTROL_STAMP> <CONTROL_DATE> 40(45)
41 </CONTROL_DATE> <CONTROL_USER/> </CONTROL_STAMP> <!-- Acceptance stamp --> <ACCEPTANCE_STAMP> <ACCEPTANCE_DATE> </ACCEPTANCE_DATE> <ACCEPT_USER/> </ACCEPTANCE_STAMP> <!-- Free text --> </ROW> </ROWS> <!-- Invoice summary information, mandatory --> <SUMMARY> <!-- Product rows together, VAT -attribute mandatory --> <ROWS_TOTAL> </ROWS_TOTAL> <!-- Invoice total sum, mandatory element, VAT -attribute mandatory --> <!-- INVOICE_TOTAL/AMOUNT with VAT-attributes tells taxable and non-taxable invoice sum --> <INVOICE_TOTAL> </INVOICE_TOTAL> <!-- Insurance total, VAT -attribute mandatory --> <INSURANCE_TOTAL> </INSURANCE_TOTAL> <!-- Vat sums in different tax base --> <!-- Optional attribute VAT_TYPE, identifier for tax type --> <VAT_SUMMARY VAT_TYPE=""> <!-- Tax-% --> <RATE/> <!-- Basis for tax --> <ACCORDING> </ACCORDING> <!-- Additional information for tax base --> <VAT_ADDITIONAL_INFO> <VAT_INFO> <BASE_DESCRIPTION/> <BASE_AMOUNT> </BASE_AMOUNT> </VAT_INFO> </VAT_ADDITIONAL_INFO> <!-- Tax total --> <VAT_RATE_TOTAL> </VAT_RATE_TOTAL> <!-- Taxable amount total --> <VAT_GROUP_TOTAL> </VAT_GROUP_TOTAL> <!-- Tax account --> <DEFAULT_VAT_RATE_ACCOUNT/> 41(45)
42 <!-- Additional information for tax --> <VAT_DESCRIPTION/> <!-- Currency for tax --> <CURRENCY_CODE/> </VAT_SUMMARY> <!-- Tax sum for Invoice --> <VAT_TOTAL> </VAT_TOTAL> <!-- Tax account --> <DEFAULT_VAT_ACCOUNT/> <!-- Rounding --> <ROUNDINGS/> <!-- Discount for whole invoice, alternative structure for DISCOUNTS_FROM_TOTAL and DISCOUNTS_TOTAL -elements--> <!-- Discount type in TYPE-attribute: 00/empty = normal, 02 = contract discount --> <DISCOUNT TYPE=""> <!-- Discount description --> <DISCOUNT_NAME/> <!-- Discount-% --> <PER_CENT/> <!-- Total discount, VAT -attribute mandatory --> <DISCOUNT_AMOUNT> </DISCOUNT_AMOUNT> </DISCOUNT> <!-- Invoice discount (from the amount), VAT -attribute mandatory --> <DISCOUNTS_FROM_TOTAL> </DISCOUNTS_FROM_TOTAL> <!-- Invoice discount, VAT -attribute mandatory --> <DISCOUNTS_TOTAL> </DISCOUNTS_TOTAL> <!-- Total surcharge for the invoice, VAT -attribute mandatory --> <SURCHARGE_TOTAL> </SURCHARGE_TOTAL> <!-- Freight (invoice specific), VAT -attribute mandatory --> <CARGO> </CARGO> <!-- Extra for delivery (invoice specific), VAT -attribute mandatory --> <DELIVERY_EXTRA> </DELIVERY_EXTRA> <!-- Advance payment, VAT -attribute mandatory --> <ADVANCE_PAYMENT> </ADVANCE_PAYMENT> <!-- Total interest, VAT -attribute mandatory --> <INTEREST_CHARGE> </INTEREST_CHARGE> <!-- Total collection surcharge, VAT -attribute mandatory --> <COLLECTION_SURCHARGE_TOTAL> </COLLECTION_SURCHARGE_TOTAL> <!-- Provision --> <COMMISSION> <!-- Provision name --> <COMMISSION_NAME/> <!-- Per cent --> <PER_CENT/> 42(45)
43 <!-- Sum, VAT -attribute mandatory --> <COMMISSION_AMOUNT> </COMMISSION_AMOUNT> </COMMISSION> <!-- Total postage costs, VAT -attribute mandatory --> <POSTAGE_COSTS> </POSTAGE_COSTS> <!-- Total processing costs, VAT -attribute mandatory --> <PROCESSING_COSTS> </PROCESSING_COSTS> <!-- Invoice total in other currency, VAT -attribute mandatory --> <INVOICE_TOTAL_IN_OTHER_CURRENCY> <CURRENCY> <CODE/> <RATE/> </CURRENCY> </INVOICE_TOTAL_IN_OTHER_CURRENCY> <!-- Information costs total, VAT -attribute mandatory --> <TOTAL_INFO_COSTS> </TOTAL_INFO_COSTS> <!-- Advance income-tax, VAT -attribute mandatory --> <INCOME_OF_TAX_WITHELD_IN_ADVANCE> </INCOME_OF_TAX_WITHELD_IN_ADVANCE> <!-- Link, optional attributes TYPE and OBJECT --> <LINKS> <LINK TYPE="" OBJECT=""/> </LINKS> <!-- Free text --> </SUMMARY> <!-- Information for partial payments --> <PART_PAYMENTS> <PAYMENT> <!-- Part identifier --> <PART_ID/> <!-- Number of partial payments --> <PART_COUNT/> <!-- Part due date --> <PART_DUE_DATE> </PART_DUE_DATE> <!-- Unpaid amount, VAT -attribute mandatory --> <UNPAID> </UNPAID> <!-- Start date of period --> <START_PERIOD> 43(45)
44 <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> <!-- alternatively invoicing period as text string --> <PERIOD_TEXT/> </START_PERIOD> <!-- End date of the period --> <END_PERIOD> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> </END_PERIOD> <!-- Partial payment, VAT -attribute mandatory --> <PARTIAL_PAYMENT> </PARTIAL_PAYMENT> <!-- Interest --> <INTEREST> <!-- Per cent --> <PER_CENT/> <!-- Monetary amount --> </INTEREST> <!-- Processing costs, VAT -attribute mandatory --> <PROCESSING_COSTS> </PROCESSING_COSTS> <!-- To be paid amount, VAT -attribute mandatory --> <PART_SUM> </PART_SUM> <!-- Payment reference --> <PAYMENT_REFERENCE/> <!-- Free text --> </PAYMENT> </PART_PAYMENTS> <!-- Finvoice EpiDetails -structure --> <EpiDetails> <EpiIdentificationDetails> <EpiDate Format=""/> <EpiReference/> <EpiUrl/> <Epi /> <EpiOrderInfo/> </EpiIdentificationDetails> <EpiPartyDetails> <EpiBfiPartyDetails> 44(45)
45 <EpiBfiIdentifier IdentificationSchemeName=""/> </EpiBfiPartyDetails> <EpiBeneficiaryPartyDetails> <EpiNameAddressDetails/> <EpiBei/> <EpiAccountID IdentificationSchemeName=""/> </EpiBeneficiaryPartyDetails> </EpiPartyDetails> <EpiPaymentInstructionDetails> <EpiPaymentInstructionId/> <EpiTransactionTypeCode/> <EpiInstructionCode/> <EpiRemittanceInfoIdentifier IdentificationSchemeName=""/> <EpiInstructedAmount AmountCurrencyIdentifier=""/> <EpiCharge ChargeOption=""/> <EpiDateOptionDate Format=""/> </EpiPaymentInstructionDetails> </EpiDetails> <!-- Digital signature --> <DIGITAL_SIGNATURE SIGNATURE_LENGTH=""/> <!-- Timestamp --> <CONTROL_TIMESTAMP> <TIME> <HOUR/> <MINUTE/> <SECOND/> </TIME> <ZONE/> </CONTROL_TIMESTAMP> <!-- Invoice specific request for acknowledgement, payee and payer have to agree usage --> <FB_REQUEST/> </INVOICE> </INVOICES> </CONTENT_FRAME> </INVOICE_CENTER> 45(45)
TEAPPSXML version 2.7
18.12.2006 1 (40) 18.12.2006 2 (40) Table of contents 1 Introduction... 4 1.1 Tree-structure notation... 4 1.2 Entities... 5 1.3 Decimal separator... 5 1.4 The number of decimals... 5 1.5 Spaces, prefix
e2b Invoice Format Message Description Version: 3.4
06.12.2007 CHANGE LOG DATE VER DONE BY CHANGES 06.12.2007 3.4 Lars Olavesen Ref. Change log: www.e2b.no 22.06.2007 3.3.1 Are Berg Corrected in chapter 3.7 Message description which differs from XML Schema
Business Document Specification Issue date: 2011-03-01 Version: 1.61 Invoice 20.1.6 Belonging message specification: MS 35
This business document is used when invoicing delivered and returned trade items. One invoice corresponds to one delivery or one return. The transaction is also used when crediting. If a calloff has been
GUIDE ON GST ACCOUNTING SOFTWARE FOR SOFTWARE DEVELOPERS IN MALAYSIA UNIT TUGAS-TUGAS KHAS GST JABATAN KASTAM DIRAJA
GUIDE ON GST ACCOUNTING SOFTWARE FOR SOFTWARE DEVELOPERS IN MALAYSIA UNIT TUGAS-TUGAS KHAS GST JABATAN KASTAM DIRAJA TABLE OF CONTENTS 1. INTRODUCTION 1 2. IMPORTANCE OF ACCOUNTING SOFTWARE FOR BUSINESSES
Book Industry Communication
Book Industry Communication e4books Web Services Standards Post Financial ocument Version 0.9, 20 November 2007 This document specifies in human-readable form the e4books web services Post Financial ocument
Infor LN Financials User Guide for Cash Management
Infor LN Financials User Guide for Cash Management Copyright 2015 Infor Important Notices The material contained in this publication (including any supplementary information) constitutes and contains confidential
How To Get A Credit Card From A Bank With A Creditcard
Invoic M 1.. 1 InvoicHeader M 1.. 1 InvoiceTypeNeB M 1.. 1 InvoiceNumber M 1.. 1 DocumentDate O 0.. 1 ActualDeliveryDate O 0.. 1 DeliveryPeriodStartDate O 0.. 1 DeliveryPeriodEndDate O 0.. 1 ReasonForCreditingNeBType
S A G E P A S T E L P A R T N E R V E R S I O N 1 2 V e r s i o n 1 2. 1 T r a i n i n g M a n u a l L e s s o n 4
V e r s i o n 1 2. 1 T r a i n i n g M a n u a l L e s s o n 4 [ Lesson 4 ] Using the Auto Setup [ Learning Outcomes ] During the course of this lesson, you are going to set up a company using the auto
February 2010 Version 6.1
HansaWorld University Point Of Sales (POS) Training Material HansaWorld Ltd. February 2010 Version 6.1 Table Of Contents INTRODUCTION...5 What is Point Of Sales?...5 THE 4 DIFFERENT WAYS OF USING POS...6
www.openmiracle.com SRS
www.openmiracle.com SRS Overview of OPENMIRACLE OpenMiracle is an open source accounting software, ie its sourec code is available free of cost for life time. It is an attempt to make software accounting
ENHANCE YOUR ACCOUNTING SOFTWARE TO BE GST COMPLIANT
ROYAL MALAYSIAN CUSTOMS GOODS AND SERVICES TAX GUIDE TO ENHANCE YOUR ACCOUNTING SOFTWARE TO BE GST COMPLIANT TABLE OF CONTENTS INTRODUCTION... 1 IMPORTANCE OF ACCOUNTING SOFTWARE FOR BUSINESSES... 1 GUIDANCE
Distribution Training Guide. D110 Sales Order Management: Basic
Distribution Training Guide D110 Sales Order Management: Basic Certification Course Prerequisites The combined D110 Sales Order Management certification course consists of a hands- on guide that will walk
DOCUMENT "INVOICE" USE PROFILE
DOCUMENT "INVOICE" USE PROFILE Date of release: 2009-12-11 Guide filename: UBL-TCF-UseProfile-Invoice.pdf 1. BUSINESS DESCRIPTION 1.1 This document This document is a use profile of UBL Invoice 2.0 document
Infor10 ERP Enterprise (LN) Financials. Reference Guide for Cash Management
Infor10 ERP Enterprise (LN) Financials Reference Guide for Cash Management Copyright 2011 Infor All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks
AVATAX 15 USER GUIDE
AVATAX 15 USER GUIDE Table of Contents About Avatax 15 extension Flow and integration with StoreFront Installation Connection Settings Validation & Normalization Tax Calculations GetTax details while Cart
810 Invoice ANSI ASC X12 Version 4010
810 Invoice ANSI ASC X12 Version 4010 ERICO International 31700 Solon Rd. Solon, OH 44139 7/15/2009 Purchase Order Acknowledgment Invoice-810-855 ii 7/15/2009 Purchase Order Acknowledgment Invoice-810-855
Accruals and prepayments
5 Accruals and prepayments this chapter covers... In the last chapter we have looked at the preparation of financial statements or final accounts using the extended trial balance, or spreadsheet, approach.
E-Invoicing Supplier Manual
E-Invoicing Supplier Manual Version: 1.0 2 E-Invoicing Supplier Manual Table of Contents 1 Introduction 3 1.1 About This... Manual 3 1.2 Getting Started... 3 2 Understanding E-Invoicing 4 2.1 Overview...
Sage Careline is open between 8am to 8pm, Monday to Friday, excluding public holiday Phone Support Hotline : 1300 88 SAGE (7243)
This courseware is the property of Sage Software Sdn. Bhd., and is prepared for training purposes at Sage Training Centre (STC). It covers GST features available in Sage UBS 2015 [Version 9.9.1.0] onwards.
Fusion Financials White Paper Manage Payments Business Process Prepare and Record Payments
Fusion Financials White Paper Manage Payments Business Process Prepare and Record Payments An Overview of Payments Process Author: Vijaya Gudipati Version: 1.0 Created: 14th June 2011 1 1. Table of Contents
How To Use Hansaworld Enterprise
HansaWorld Enterprise Integrated Accounting, CRM and ERP System for Macintosh, Windows, Linux, PocketPC 2003 and AIX Stock Module Program version: 5.1 2006-10-20 2006 HansaWorld Ireland Limited, Dublin,
NOTIFICATION SERVICE GUIDELINES
NOTIFICATION SERVICE GUIDELINES Version 2.0 March 2012, added ReceiverProposal, changes to message descriptions, direct payment in use 18 January 2013. 1 (2) Table of Contents 1 General... 13 2 Message
ProStix Smartstore Training Manual - Accounts Payable. 2014 Sterland Computing
ProStix Smartstore Training Manual - Accounts Payable Contents 3 Table of Contents Accounts Payable 4 1 Introduction to... Accounts Payable 4 2 Accounts Payable... Terminology 6 3 PreRequisites... 9 4
8.0.0.0.0 Accounts Receivable. I. Overview Definitions and Abbreviations. Equipment and Supplies Required
8.0.0.0.0 Accounts Receivable I. Overview Definitions and Abbreviations Equipment and Supplies Required Page 1 of 36 Revised October 2015 Version 4 II. Job Position(s) Accounts Receivable Clerk Page 2
TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK
TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK TABLE OF CONTENTS SECTION 1 General provisions... 1 I. General rules for payment execution in foreign exchange transactions...
Adagio Inventory 8.1E First Edition
Adagio Inventory 8.1E First Edition Trademark Adagio is a registered trademark of Softrak Systems Inc. All product names mentioned are trademarks or service marks of their respective owners. Copyright
Tieto Business Information exchange Portal
Tieto Business Information exchange Portal E-invoicing Issuer Web Application Guide 2.0 page 1/28 Table of Contents 1 Introduction... 3 2 Invoice Issuer web application registration... 3 3 Tieto E-invoicing
Accounting & Finance. Guidebook
Accounting & Finance Guidebook January 2012 TABLE OF CONTENTS Table of Contents... 2 Preface... 6 Getting Started... 8 Accounting... 10 Accounting Welcome... 10 Sales Quotes... 11 New Sales Quote... 11
Aplicor assumes no liability with respect to the use of the information contained herein which is provided as is and there are no warranties of any
Aplicor assumes no liability with respect to the use of the information contained herein which is provided as is and there are no warranties of any kind provided by Aplicor with respect to this document.
Transmission of delivery note and transport data in format VDA 4913
Transmission of delivery note and transport data in format VDA 4913 Table of Contents 1 Introduction... 2 2 Record formats... 2 3 Description of respective record formats... 3 3.1 record 711 (header delivery
Reference Manual Agresso Accounts Payable
Reference Manual Agresso Accounts Payable Contents Project background...1 Why Agresso?...1 Viewing Supplier Details...2 Scanning Invoices...5 Load Invoices...5 Invoice Registration...7 Overview...7 Purchase
PUBLIC. How to Manage Landed Costs. Countries: All. Solutions from SAP. SAP Business One 2007 A and 2007 B. December 2008. English
PUBLIC Countries: All Solutions from SAP SAP Business One 2007 A and 2007 B December 2008 English Contents... 3 Introduction... 3 Business Scenario Description... 3 Defining Imported Goods... 4 Defining
EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X.12-4010 Draft
EDI 210 Invoice Motor Freight 210 Invoice with Stop Offs Version: 1.0 ANSI X.12-4010 Draft Motor Freight Invoice 210 EDI Transaction. ANSI X.12 Standards Version 4010 1 Table of Contents 210 Motor Carrier
IS-XML Structure and Interface Specification for Caterers. September 2014
IS-XML Structure and Interface Specification for September 2014 1 / 23 30-Oct-14 This document may not be disclosed, reproduced, copied, recast, reformatted or transmitted in any form by any means electronic
E-invoice BGC Invoice 1.3.5
Maj 2016 E-invoice BGC Invoice 1.3.5 Bankgirocentralen BGC AB 2016. All rights reserved. www.bankgirot.se Content 1 Introduction... 6 1.1 Purpose of the document... 6 1.2 General... 6 1.3 Version history...
IDA E-PROCUREMENT PROTOCOL XML SCHEMAS INITIATIVE
IDA E-PROCUREMENT PROTOCOL XML SCHEMAS INITIATIVE E-ORDERING AND E-INVOICING PHASES Version R0.3, January 2005 2 / 82 Disclaimer "The views expressed in this document are purely those of the writer and
Introducing Your New FedEx Invoice
Introducing Your New FedEx Invoice Welcome to your New FedEx Express Invoice. To make life easier we have created a new invoice with optional formats to suit your business needs. Here is a brief explanation
E-invoice in file transfer Service description
E-invoice in file transfer Service description Content Receiving invoices through Netbank or file transfer... 3 Who can use the service?... 3 How to adopt the service... 4 File formats... 4 Finvoice...
ERPLY Accounting user guide
ERPLY Accounting user guide [email protected] Last changed: 20.10.2013 Table of Contents 1. GENERAL... 4 1.1. THE LAYOUT OF ERPLY ACCOUNTING... 4 1.2. KEY COMBINATIONS... 4 1.3. MAIN PAGE AND
Wire Transfer. Business Link. Creating a Wire Transfer Template. Wire Transfer Types. Wire Transfer Templates and Transactions
Wire Transfer Funds Mgmt Check Mgmt Reporting Administration Wire Transfers The Wire Transfer module provides a convenient and secure way to transfer funds between your accounts, or between your accounts
ERP Areas and Modules / Trading
ERP Areas and Modules / Trading These modules reflect the multi national character of the SoftBASE Business Suite. They support multiple languages, currencies, and adapt easily to cultural differences.
User guide HostLogic SAP EKAER 5.0 solution
User guide HostLogic SAP EKAER 5.0 solution version 4.4 15. July 2015 Table of Contents 1. Introduction... 3 2. Authorization... 3 3. Encryption of the EKAER password... 4 4. Master data... 6 4.1 Material
Telephone Bank. Service description
Telephone Bank Service description Content 1. Telephone Bank... 3 1.1 Technical requirements and prices... 3 1.2 Security... 3 1.2.1 Using the code card... 3 1.3 Notification of lost user ID and code card...
HansaWorld Enterprise
HansaWorld Enterprise Integrated Accounting, CRM and ERP System for Macintosh, Windows, Linux, PocketPC 2002 and AIX Quotations Program version: 4.2 2004-11-20 2004 HansaWorld Ireland Limited, Dublin,
Contents 1. Introduction... 3 2. Login... 4 3. Order Status... 5. 3.1 Search for pre-advice and orders... 5 3.2 View pre-advice or order...
Contents 1. Introduction... 3 2. Login... 4 3. Order Status... 5 3.1 Search for pre-advice and orders... 5 3.2 View pre-advice or order... 5 3.2.1 Coli... 7 3.2.2 Coli and Tracking and Tracing... 8 3.2.3
Business Document Specification Issue date: 2009-05-13 Version: 1.52 Invoice 20.1.6
Invoice Entity name: Invoice Comment: This transaction is used to invoice goods or services which have been supplied. One invoice corresponds to one delivery. If a calloff has been split into several deliveries,
TheFinancialEdge. Configuration Guide for Accounts Payable
TheFinancialEdge Configuration Guide for Accounts Payable 102312 2012 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means, electronic,
Straight2Bank Invoice Finance
Straight2Bank Invoice Finance Client User Guide Import & Export Invoice Finance Version April 2015 Overview This guide contains information which will help users navigate and familiarise with the functions
Oracle Payables Implementation Overview with screenshots Compilation of Oracle Payables Implementation notes by Ranu Srivastava ...
Compilation of Oracle Payables Implementation notes by Ranu Srivastava... Setting up Banks... Defining Internal Bank... Payables Options... Defining Payment Documents... Creating Suppliers... Overview
Optional Fields (Document and Document Lines)... 32 Setting Up Sales Taxes (VAT)... 33 Setting up Tax Definitions (Government Bodies)...
1 P a g e Contents INSTALLING PALLADIUM ACCOUNTING SOFTWARE... 10 Installing palladium on a Single Computer... 10 Installing Palladium on a workstation... 11 Server Setup... 11 Client Setup... 11 Installing
MagayaSoftware CustomizationManual
MagayaSoftware CustomizationManual Guideto AutomatingAccountingTransactions CustomizingRatesandTarifs CreatingCustom Fields CustomizingDocuments AddingJavaScripttoDocuments Magaya Software Customization
for Sage 100 ERP Accounts Payable Overview Document
for Sage 100 ERP Accounts Payable Document 2012 Sage Software, Inc. All rights reserved. Sage Software, Sage Software logos, and the Sage Software product and service names mentioned herein are registered
Administration manual
Administration manual Issued by: Operations Control, Stora Enso Logistics 1. Introduction Stora Enso has set sustainability requirements for all suppliers covering not only environmental issues, human
10. Payables Journal Entries
10. Payables Journal Entries SMARTStream Payables generates journal entries throughout the life cycle of an invoice, from the invoice processing to the payment processing and the payment clearance processing.
Overview of Procure to Pay
This segment from our 427+ page JD Edwards Accounts Payable manual is being made available as a sample of our training manuals. Please contact [email protected] if you have any JDE training needs,
Dutiable Shipments to, Russia. Service available only to Commercial Importers in Russia
Dutiable Shipments to, Russia. Service available only to Commercial Importers in Russia Strengthened control measures introduced by the Customs authorities in Russia (March 2010) to verify the full compliance
Chapter 5. Accounting for merchandising operations. Appendix 5A: Periodic inventory system
1 Chapter 5 Accounting for merchandising operations Appendix 5A: Periodic inventory system 2 Learning objectives 1. Record purchase and sales transactions under the periodic inventory system 2. Prepare
CHAPTER 9: ACCOUNTS PAYABLE SETUP
Chapter 9: Accounts Payable Setup CHAPTER 9: ACCOUNTS PAYABLE SETUP Objectives Introduction The objectives are: Create a payment schedule. Create terms of payment. Create a payment day. Set up a cash discount.
Using Microsoft Dynamics AX 2012
Exercise Guide Andreas Luszczak Using Microsoft Dynamics AX 2012 Springer Vieweg, 2nd Edition 2012 ISBN 978-3-8348-1742-6 September 2012 VI Exercise Guide Registered and/or industrial names, trade names,
HansaWorld Enterprise
HansaWorld Enterprise Integrated Accounting, CRM and ERP System for Macintosh, Windows, Linux, PocketPC 2002 and AIX Contracts 2004 HansaWorld (UK) Limited, London, England All rights reserved Program
Sophisticated Yet Simple
Sophisticated Yet Simple A SALESFORCE ADD-ON FOR ORDER FULFILLMENT AND INVENTORY MANAGEMENT You started with, it changed the way you conduct business, in fact, you now have more customers, more employees,
Credit Card Processing with Element Payment Services. Release 8.7.9
Credit Card Processing with Element Payment Services Release 8.7.9 Disclaimer This document is for informational purposes only and is subject to change without notice. This document and its contents, including
How To Use Standard Pos On A Pc Or Macbook Powerbook 2.5.2.2 (Powerbook 2)
Integrated Point of Sales System for Mac OS X Program version: 6.3.22 110401 2012 HansaWorld Ireland Limited, Dublin, Ireland Preface Standard POS is a powerful point of sales system for small shops and
Invoice, Statement, and Deposit Slip Layout Variables
CLIENT BOOKKEEPING SOLUTION ACCOUNTS RECEIVABLE Invoice, Statement, and Deposit Slip Layout s version 2007.x.x TL 20756 (05/29/09) Copyright Information Text copyright 997-2009 by Thomson Reuters/Tax &
CHAPTER 6: SALES ORDERS
Chapter 6: Sales Orders CHAPTER 6: SALES ORDERS Objectives Introduction The objectives are: Review the various forms and list pages for working with sales orders. Determine and apply different sales order
VAT invoice requirements in Germany
Tax Services / Leaflet, October 2013 VAT invoice requirements in Germany Businesses trading in Germany should ensure using the correct VAT rate to account for German VAT. The standard VAT rate is currently
4. Do not make changes to the Master record. To create a custom form, click Copy.
Custom Invoice Import Custom imports allow for the creation of Munis invoices through a fixed or delimited file import. Customization of the import form can be edited to fit an existing export or report
Accounts Payable and Cash Payments Overview. Dan Aldridge
Accounts Payable and Cash Payments Overview Dan Aldridge Finance Training Agenda ACR & CMG ACR - Accounts Payable Overview Overview Master Data Processing Open Entries Exercises CMG - Cash Management Overview
ACCOUNT RECEIVABLES TABLE OF CONTENTS
ACCOUNT RECEIVABLES TABLE OF CONTENTS 1. SETUP CUSTOMER...2 2. CUSTOMER LISTING...6 3. CUSTOMER INVOICE...7 4. CUSTOMER INVOICE LISTING...12 5. ENTER CREDITS / REFUNDS...14 6. CUSTOMER CREDITS LISTING...20
OBIEE Dashboard Reporting Reference Guide
Oracle 12 Finance Training OBIEE Dashboard Reporting UK SBS Training Services Team Version Control Version Created Author Reviewer Signed Off 2.0 MAY-2014 M. Houghton D. Rees 19.06.14 Page ii Contents
Invoice Line Export. Guide
Invoice Line Export Save time and avoid entering booked invoices manually in the financial system Guide Get started with Invoice Line Export This document describes how TimeLog Project s function for export
Comparison of Alteris BMS and SBE
General Multi User Capable 1 or 3 No Limit Additional Licenses Required Barcode Scanners Select Models Cash Drawers Select Models Customer Pole Displays Select Models 40 Column Receipt Printers Select
Straight2Bank Receivables Services
Straight2Bank Receivables Services Client User Guide Document-Level Financing Version April 2015 Overview This guide contains information which will help users navigate and familiarise with the functions
Agenda. Lecture Chapter 9 Quiz Chapter 8 Exercises & Problem Chapter 8. Objective. Cash Receipts. Cash Receipts, Payments, & Banking Procedures
Cash Receipts, Payments, & Banking Procedures Agenda Lecture Chapter 9 Quiz Chapter 8 Exercises & Problem Chapter 8 Cash Receipts, Payments, & Banking Procedures Objective Cash Receipts 1.cash receipts
Invoice Entry. Field Descriptions. A number used to identify the batch. This number must be unique for each user. Batch
Invoice Entry Objective The Invoice Entry screen allows the entry of invoices, credit memos, wire transfers, and direct disbursements in batch mode. When batches are complete, they are proofed, posted,
Matching, Amending and Foreign Invoices in Accounts Payable
Matching, Amending and Foreign Invoices in Accounts Payable Table of Contents 1. Overview of Matching an External Invoice... 3 2. Matching an Invoice to a Purchase Order... 4 3. Additional Charges for
How to: Account for Settlement Discount VAT Rule Changes from 1 st of April 2015
How to: Account for Settlement Discount VAT Rule Changes from 1 st of April 2015 Users of Merlin who offer Settlement Discount to their Customers, or are given Settlement Discount by their Suppliers, will
User Manual. CitiDirect \ CitiDirect EB - Citi Trade Portal. InfoTrade Phone No. 0 801 258 369 [email protected]
CitiDirect \ CitiDirect EB - Citi Trade Portal User Manual InfoTrade Phone No. 0 801 258 369 [email protected] CitiDirect HelpDesk Phone No. 0 801 343 978, +48 (22) 690 15 21 Monday Friday 8.00 17.00
County of Henrico ACCOUNTS PAYABLE ORACLE UPGRADE R12
County of Henrico ACCOUNTS PAYABLE ORACLE UPGRADE R12 08/01/2014 ACCOUNTS PAYABLE Oracle Payables Invoice Types... 3 Query Invoice Records... 4 Create Invoice Batches... 6 Enter a Direct Pay Invoice...
General Dynamics Armament & Technical Products 8/30/2010
Supplier s Guide to isupplier Portal General Dynamics Armament & Technical Products 8/30/2010 Page 1 of 192 8/30/2010 Contents Procurement Notification Workflow... 6 Purchase Order Entry and Acknowledgement...
CHAPTER 1: SALES ORDER MANAGEMENT
Chapter 1: Sales Order Management CHAPTER 1: SALES ORDER MANAGEMENT Objectives Introduction The objectives are: Review the setup of Sales Order Management, including customers, shipping options, reservation
BaanERP (Grieg SP4) Definition of BEMIS V DIS001A Import and Export File for the EDI Business Document Dispatch Advise
BaanERP (Grieg SP4) Definition of BEMIS V DIS001A Import and Export File for the EDI Business Document Dispatch Advise A publication of: Baan Development B.V. P.O.Box 143 3770 AC Barneveld The Netherlands
810 Invoice Revised 01/26/15
Functional Group ID=IN Introduction: This Standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange
Integrated Accounting, CRM and ERP System for Mac OS X, Windows, Linux, ios, Android and AIX
Integrated Accounting, CRM and ERP System for Mac OS X, Windows, Linux, ios, Android and AIX Purchase Order Contract Register Program version: 7.2 140321 2014 HansaWorld Ireland Limited, Dublin, Ireland
Visma Solutions Oy. Netvisor and Netvisor Easy. Service description. Lappeenranta Visma Solutions Oy Valtakatu 51 53100 Lappeenranta FINLAND.
Netvisor and Netvisor Easy Service description 1 SUMMARY This document describes the Netvisor service and Netvisor Easy service (hereinafter Easy service) of (hereinafter Visma Solutions) and the bases
Important: Please follow regional 3M invoicing guidelines for one PO per invoice.
Job Aid Create and Publish Invoice with SNC (Supplier) EN Use this Supplier portal activity to create and publish an invoice from an Advance Shipping Notification (ASN). Important: Please follow regional
Alma Invoices for Finance One
Alma Invoices for Finance One Finance One payment data The CSV file 3 or more lines per invoice, invoices numbered within file, lines numbered within invoice first line has the payment amount second line
Oracle 12 Finance Training Receipting & Purchase to Pay Best Practice Reference Guide
Oracle 12 Finance Training Receipting & Purchase to Pay Best Practice UK SBS Training Services Team Contents 1 Purchase to Pay Processes... 1 1.1 Non Catalogue Requisition Process... 1 1.2 Smart Form Requisition
TERMS AND CONDITIONS OF CASH TRANSACTIONS IN DOMESTIC TRANSACTIONS AT PKO BP SA BANK
TERMS AND CONDITIONS OF CASH TRANSACTIONS IN DOMESTIC TRANSACTIONS AT PKO BP SA BANK TABLE OF CONTENTS Section 1... 1 GENERAL PROVISIONS... 1 I. Acceptance and execution of the payment order by the Bank...
Application Programming Interface (API)
Integration to Salesforce CRM Create a Recurring Billing Contract from an Opportunity in one click. Create a Sales Order from an Opportunity in one click. Create a Project from a list of pre- defined templates
Accounts Payable Entry Tips
[MU-FN-6-E] [MU-FN-10-E) Accounts Payable Entry Tips Munis-Financials: Accounts Payable CLASS DESCRIPTION This class will examine new ways to improve efficiency and streamline functionality within the
Reports Pack. TherapySource and Rehab ToolKit. Version 1.1
Reports Pack TherapySource and Rehab ToolKit Version 1.1 February 2009 TABLE OF CONTENTS THERAPYSOURCE... 6 SCHEDULING REPORTS... 6 Appointment Card... 6 Daily Call List... 6 Daily Sign-In Sheet... 7 Cancelled,
FSD Finance One User Manual Accounts Payable Last update: October 2013
i FSD Finance One User Manual Accounts Payable Last update: October 2013 Accounts Payable Table of Contents AP1.0 Invoice Entry (APINV)... 1 AP2.0 Accounts Payable Ledger Enquiries... 8 AP3.0 Additional
Accounts Payable. Best Practices: Existing Control: Control Gap: Controls Evaluation and Gap Analysis. Purchasing
Accounts Payable Gap Analysis: POS identifies the following Best Practices as efficient and effective control processes for the above risk. Listed for comparison are the controls currently in place, if
IFS FINANCIALS 7.5 DEVELOPMENT HISTORY
www.ifsworld.com www.ifsworld.com DEVELOPMENT HISTORY HANS SJÖQVIST CHIEF ADVISER, IFS FINANCIALS RELEASE AND SERVICE PACK HISTORY First released October 11 th 2007 Service Pack 1 released March 7 th 2008
