© 2018 Capita Business Services Ltd. All rights reserved.

Capita Education Software Solutions is a trading name of Capita Business Services Ltd. Our Registered office is 30 Berners Street, London, W1T 3LR and our registered number is 02299747. Further information about Capita plc can be found in our legal statement.

SIMS 7 - Fees Integration

Background

SIMS Fees Ledger has been designed to allow it to interface with Accounting Packages.  It supports both code and file data exchange which are all XML based.

What can be exchanged?

Chart of Accounts

The accounting structure is required to allow transactions to be exported from SIMS Fees in to the accounting system.  This allows for charges and receipts to be coded against say ledger codes.

Fiscal Calendar

Charges and receipts typically need to be recorded against a financial period.  SIMS Fees supports imports of a fiscal calendar to enable the accounting periods to be exported along with the charges and receipts.

Transactions

Fees can export charges and receipts to an accounting package.

What formats are available

For all of the above SIMS Fees supports:

              A programmatic interface [Fees Plugin]

              XML File based Interface

              Text File based interface

Formats for the files and API details will be made available to SIMS Technical Partners on request.

Whilst the Fees APIs are available for partner use, we would recommend that partners either use the file based data exchange or create a Fees Plugin.  The plugin would implement a set of required interfaces for the above. 

<?xml version="1.0" encoding="utf-8" ?>
<!-- Created with Liquid XML Studio 1.0.8.0 (http://www.liquid-technologies.com) -->
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://capita.co.uk/sims/fees/xmlplugin" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="Journals">
    <xs:complexType>
      <xs:sequence>
        <xs:element minOccurs="1" name="Journal">
          <xs:complexType>
            <xs:sequence>
              <xs:element minOccurs="1" maxOccurs="unbounded" name="Transaction">
                <xs:complexType>
                  <xs:sequence>
                    <xs:element minOccurs="1" name="BillTerm" />
                    <xs:element minOccurs="1" name="BatchNumber" type="xs:string" />
                    <xs:element minOccurs="1" name="BatchDescription" type="xs:string" />
                    <xs:element minOccurs="1" name="SeqNo" type="xs:string" />
                    <xs:element minOccurs="1" name="SourceType" type="xs:string" />
                    <xs:element minOccurs="1" name="TransactionCode" type="xs:string" />
                    <xs:element minOccurs="1" name="Description" type="xs:string" />
                    <xs:element minOccurs="1" name="GLAccount" type="xs:string" />
                    <xs:element minOccurs="1" name="VATCode" type="xs:string" />
                    <xs:element minOccurs="1" name="Amount" type="xs:string" />
                    <xs:element minOccurs="1" name="VATAmount" type="xs:string" />
                    <xs:element minOccurs="1" name="PupilRef" type="xs:string" />
                    <xs:element minOccurs="1" name="PayerRef" type="xs:string" />
                    <xs:element minOccurs="1" name="BillNumber" />
                    <xs:element minOccurs="1" name="GiroNumber" />
                    <xs:element minOccurs="1" name="ChargeCodeType" />
                    <xs:element minOccurs="1" name="FinancialYear" type="xs:string" />
                    <xs:element minOccurs="1" name="FinancialPeriod" type="xs:string" />
                    <xs:element minOccurs="1" name="Date" type="xs:string" />
                    <xs:element minOccurs="1" name="Reference" type="xs:string" />
                    <xs:element minOccurs="1" name="FeesControlAccount" type="xs:string"/>
                    <xs:element minOccurs="1" name="PostInDetail" type="xs:string" />
                    <xs:element minOccurs="1" name="CG" type="xs:string" />
                  </xs:sequence>
                </xs:complexType>
              </xs:element>
            </xs:sequence>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
	<xs:attribute name="schemaversion" type="xs:string" use="optional"  fixed="1.0"/>
      <xs:attribute name="creationdate" type="xs:string" use="optional" />
    </xs:complexType>
  </xs:element>
</xs:schema>

 

Technical Integrator 

We would recommend that third parties who wish to interface with SIMS Fees should be:

  • SIMS Technical Integrators
  • Have a Development Support Subscription
  • Have a SIMS Subscription

We would also recommend that any plugin should be accredited by Capita.

The of file only based data exchange would not attract per site fees, however other integrations would attract per site fees.

See https://www.capita-sims.co.uk/partner-with-us  for current charge rates.

Becoming a Technical Integrator

Again see  https://www.capita-sims.co.uk/partner-with-uss for instructions and guidance or contact partner.management@capita.co.uk for commercial discussions or contact partner.support@capita.co.uk for any clarification on technical matters.