Kuali Financial System Interface Specification for Electronic Invoice Feed



Similar documents
Kuali Security Request Installation Guide

Extensible Markup Language (XML): Essentials for Climatologists

Kuali Requisition Training

E-Invoice Interface File Layout Version 4.93

Electronic Data Transmission Guide For International Mailers

An XML Based Data Exchange Model for Power System Studies

Electronic Invoicing Overview. April, 2010

Exchanger XML Editor - Canonicalization and XML Digital Signatures

Data Integration through XML/XSLT. Presenter: Xin Gu

Invoice Processing Automation

xmlns:emcs=" xmlns:tms="

A/P Payment Selection Based on A/R Cash Receipts AP-1108

SEPA formats - an introduction to XML. version September

MAS 90 Demo Guide: Accounts Payable

XMW. Electronic Reporting System in XML format. Payment statistics

Synergist Spotlight on

Division of Finance and Budget Strategic Plan

New York State Federal/State Employment Tax (FSET) Handbook for Software Developers

PDF Invoicing. Dispelling the Myths. My suppliers want to send PDF invoices are these the same as electronic invoices?

XML: extensible Markup Language. Anabel Fraga

Accounts Payable Expense Distribution Tables

Accounts Receivable Module Customer Invoice

Release Notes: BUSINESS PRO GENERAL LEDGER VERSION 3.0 BUSINESS PRO ACCOUNTS PAYABLE VERSION 4.0

E-Invoicing Supplier Manual

Generate Electronic Payments in Accounts Payable

SEO Deployment Best Practices

Introduction to Web Services

Managing XML Documents Versions and Upgrades with XSLT

Grandstream XML Application Guide Three XML Applications

DocuSign Quick Start Guide. Using the Bulk Recipient Feature. Overview. Table of Contents

XML message for Payment Initiation Implementation Guideline. Version 1.02

Instead, there should only be one URL for the home page to avoid duplication.

Table of Contents. OTC AP Revenue Refund Process

AP Invoice Processing AP Invoice Entry MUNIS Version 8

CENTRAL SUSQUEHANNA INTERMEDIATE UNIT Application: Fund Accounting

HTML Web Page That Shows Its Own Source Code

Fast track to HTML & CSS 101 (Web Design)

>

Web Development I & II*

Accounts Payable Job Aid

University of Hawaii Capital Asset

Accounts Payable Version 6.1 Release Notes

Introduction to the Data Migration Framework in Microsoft Dynamics by Ruben Barron

Accounts Payable Invoice Data Import AP-1012

Accounts Receivable. Chapter

StreamServe Persuasion SP5 Document Broker Plus

Corporate Online. Import format for Payment Processing Service files

Customizing MISys Manufacturing Reports Using ADO-XML 6/3/2013

1) ONEGATE, THE NEW PORTAL TO SUBMIT REPORTS TO THE NATIONAL BANK OF BELGIUM

TROUBLESHOOTING XML WHAT IS XML? 4/27/2015. Jim Hines CEPI Customer Support Manager

Inventory Update API User Documentation

COUNTY OF MENDOCINO. MUNIS Finance System How to Enter an Invoice. Created by: Auditor-Controller May 2007 v1

Standard Operating Procedure. 1. Purpose

NewHomeSource and Move New Homes platform Consumer leads reporting

Oracle Cloud Expenses Co-existence and Integration Options

XSLT Mapping in SAP PI 7.1

Accounting for Credit Card Transactions. Tips and Tools for Reconciling Credit Card Terminals and IU Pay Plus

Foreign Account Tax Compliance Act (FATCA) Foreign Account Tax Compliance Act (FATCA) FATCA Reports

Importing Data from a Dat or Text File into SPSS

Internationalization Tag Set 1.0 A New Standard for Internationalization and Localization of XML

ART 379 Web Design. HTML, XHTML & CSS: Introduction, 1-2

Cleo Communications. CUEScript Training

Digital Data & Image Format Guidelines For School Photography and Yearbook Publication Version

enicq 5 External Data Interface User s Guide

[MS-ASMS]: Exchange ActiveSync: Short Message Service (SMS) Protocol

ESPO. E-Commerce. An ESPO How To Guide

ERP Commerce Connect Feature Summary 1.0.1

Importing Lease Data into Forms Online

Self-serve Incentive Program (SIP) User Guide Version 3.0. For use by Industrial Customers for Lighting System and Compressed Air projects

Secure XML API Integration Guide. (with FraudGuard add in)

Using GABRIEL Excel to XML Templates

Appendix report 1: Syntax and structure of EDIFACT and XML messages Regulation F1:

Country-specific update for Mexico

1. Create a web page which will contain image of window layout as follows.

Master Card International. Common Data Format (CDF) 3 Release XML Data Format

Advertisers: how to provide an RSS feed to Reactivpub

Improved Navigation Magento Extension User Guide

KFS Cash and Accounts Receivable A Procedural Guide for Kuali Financial Systems E-Docs Kuali Implementation Team

Best-Practice Automation of Invoice Delivery from ERP Systems

EnergyCAP / Purchased Utilities

JavaScript: Introduction to Scripting Pearson Education, Inc. All rights reserved.

Accounting for Credit Card Transactions

12 The Semantic Web and RDF

Developer Guide to Authentication and Authorisation Web Services Secure and Public

PEOPLESOFT ENTERPRISE esettlements

Invoice Approval - Paying Invoices

Business Partner Master Data (LO-MD-BP)

ACE: Dreamweaver CC Exam Guide

CONTRACT MODEL IPONZ DESIGN SERVICE VERSION 2. Author: Foster Moore Date: 20 September 2011 Document Version: 1.7

About XML in InDesign

DEMO ONLY VERSION. Easy CramBible Lab M Magento Front End Developer Certification Exam. ** Single-user License **

Transcription:

Kuali Financial System Interface Specification for Electronic Invoice Feed Overview The current financial system used at Cornell will be replaced by the Kuali Financial System (KFS). This will occur July 1, 2011 for fiscal year 2012. The Electronic Invoice (einvoice) feeds currently being fed to the legacy financial system from external vendors will need to be rewritten to conform to the KFS einvoice Upload format. The location where these feeds are sent will also need to be changed. The purpose of this document is to describe the KFS einvoice file layout. NOTE: The location where the files will need to be sent, as well as the mechanism behind this communication medium has not been finalized at this time. The method for feeding einvoices to KFS is a feature of the Accounts Payable Batch Process. The data file uses the cxml format for Invoices. Data File Layout The einvoice file must begin with the standard XML version line. The root (first) tag for einvoice files must be the <cxml> tag and the file must contain only one set of <cxml></cxml> tags. This tag also contains attributes that identify the schema the document adheres to. (See sample file below.) Following the <cxml> tag must be the <header> tag. This section gives general information about the set of records being transmitted. Like the <cxml> tag, the file must contain only one <header></header> tag. Within the header tag are other tags that identify pieces of header information. Next comes a <request> tag. This tag contains other tags that represent the individual fields of the payee and the payment transaction. Each <request></request> tag represents one payment transaction. Within each <request> tag is the <invoicedetailrequest> tags. Each <invoicedetailrequest> tag contains an <invoicedetailrequestheader>, <invoicedetailorder> and an <invoicedetailsummary> tag. 1 Kuali Financial System Interface Specifications Cornell University

einvoice File Format File must begin with the xml declaration. <?xml version="1.0" encoding="utf-8"?> The root (first) tag for einvoice files must be the <cxml> tag, and the file must contain only one <cxml></cxml> tag. This tag also contains attributes that identify the schema the document adheres to, such as: <cxml xmlns= http://www.kuali.org/kfs/purap/electronicinvoice" xmlns:purap=http://www.kuali.org/kfs/purap/types xmlns:kfs=http://www.kuali.org/kfs/sys/types xmlns:xsd="http://www.w3.org/2001/xmlschema > Following the header will be one or more requests for payment identified by the <request> tag. Each request references a single payment and must also contain a <detail> section identifying the accounting distribution for that payment in one or more <accounting> tags. After the final group the file must end with a <trailer> specifying the total detail count and amount in the file. The format for the data file is defined by the cxml consortium. This format can be found at http://xml.cxml.org/current/cxmlusersguide.pdf. Chapter 11 of this user s guide discusses Invoices, and outlines the values and format of the electronic invoice file that KFS uses. Example Electronic Invoice Upload File: <?xml version="1.0" encoding="utf-8"?> <cxml payloadid="200807260401062080.964@eai002" timestamp="2008-07-26t04:01:06-08:00" version="1.2.014" xml:lang="en" xmlns="http://www.kuali.org/kfs/purap/electronicinvoice" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance"> <Header> <From> <Credential domain="duns"> <Identity></Identity> </From> <To> <Credential domain="networkid"> <Identity>IU</Identity> </To> <Sender> <Credential domain="duns"> <Identity></Identity> <UserAgent/> </Sender> </Header> <Request deploymentmode="production"> 2 Kuali Financial System Interface Specifications Cornell University

<InvoiceDetailRequest> <InvoiceDetailRequestHeader invoicedate="11/22/2010" invoiceid="1186916436" operation="new" purpose="standard"> <InvoiceDetailHeaderIndicator/> <InvoiceDetailLineIndicator/> <InvoicePartner> <Contact addressid="966217331" role="billto"> <Name xml:lang="en">it - EAST HILL PLAZA PINE TREE,341</Name> <Street>NA</Street> <City>Ithaca</City> <PostalCode>14853</PostalCode> <Email name="dms386@cornell.edu">dms386@cornell.edu</email> <Phone name="607-255-0870"> <TelephoneNumber> <CountryCode isocountrycode="us">1</countrycode> <AreaOrCityCode>607</AreaOrCityCode> <Number>-255-0870</Number> </TelephoneNumber> </Phone> </InvoicePartner> <InvoicePartner> <Contact addressid="1461059812" role="remitto"> <Name xml:lang="en"> Jones Appliance </Name> <Street>ehob</Street> <City>ithaca</City> <PostalCode>14850</PostalCode> </InvoicePartner> <InvoiceDetailShipping> <Contact addressid="1586544660" role="shipto"> <Name xml:lang="en">it - EAST HILL PLAZA PINE TREE,341</Name> <Street>NA</Street> 3 Kuali Financial System Interface Specifications Cornell University

<City>Ithaca</City> <PostalCode>14853</PostalCode> <Email name="dms386@cornell.edu">dms386@cornell.edu</email> <Phone name="607-255-0870"> <TelephoneNumber> <CountryCode isocountrycode="us">1</countrycode> <AreaOrCityCode>607</AreaOrCityCode> <Number>-255-0870</Number> </TelephoneNumber> </Phone> </InvoiceDetailShipping> </InvoiceDetailRequestHeader> <InvoiceDetailOrder> <InvoiceDetailOrderInfo> <OrderReference orderdate="11/22/2010" orderid="1022"> <DocumentReference payloadid="na" /> </OrderReference> </InvoiceDetailOrderInfo> <InvoiceDetailItem invoicelinenumber="1" quantity="10.00"> <UnitOfMeasure>EA</UnitOfMeasure> <UnitPrice> <Money currency="usd">500.00</money> </UnitPrice> <InvoiceDetailItemReference linenumber="1"> <ItemID> <SupplierPartID></SupplierPartID> </ItemID> <Description xml:lang="en">cases</description> </InvoiceDetailItemReference> <SubtotalAmount> <Money currency="usd" >5000.0000</Money> </SubtotalAmount> </InvoiceDetailItem> </InvoiceDetailOrder> <InvoiceDetailSummary> <SubtotalAmount> </SubtotalAmount> <Tax> <Description xml:lang="en">total Tax</Description> </Tax> <SpecialHandlingAmount> </SpecialHandlingAmount> <ShippingAmount> 4 Kuali Financial System Interface Specifications Cornell University

</ShippingAmount> <GrossAmount> </GrossAmount> <InvoiceDetailDiscount> </InvoiceDetailDiscount> <NetAmount> </NetAmount> <DepositAmount> </DepositAmount> <DueAmount> </DueAmount> </InvoiceDetailSummary> </InvoiceDetailRequest> </Request> </cxml> General XML Rules All elements (tags) must have a closing tag. Tags are case-sensitive A tag must not contain extra whitespace (blanks) at the beginning or end. Tags must not be empty. If there is no value for the field (and it is not required) then do not render the element. Coding of special characters: Description Desired character Syntax Example Less than < < <deptname>b<fs</deptname> Greater than > > <deptname>b>fs</deptname> Ampersand & & <deptname>b&fs</deptname> Apostrophe &apos; <deptname>b&apos;fs</deptname> Quotation mark " <deptname>b"fs</deptname> 5 Kuali Financial System Interface Specifications Cornell University