InTime Export Errors

The IBAN record on the workers details is likely to be invalid. There are a number of internet sites offering IBAN number validation including - http://www.xe.com/ibancalculator/ OR - https://www.iban.com/ 

Case 51848. Customer resolved following identification that the year end processing had not been completed.

Check the Department field on the Consultants record is populated.

Item: Client Invoice for Client Name (Invoice Number AAA) with 1 lines for Document label

Error: Failed to send Invoice Number AAA to Twinfield: transaction 1 header office: Company NULL does not exist

Case 55216

This is because the Payment Terms have been changed. Previously there were 2 PT's for the client. In this instance one has been renamed and the other removed.
The Twinfield export configuration uses the payment term name to determine the database so it was no longer working.

Solution. Update the Twinfield export configuration.

 The user should advise Support when they want to make changes to the Payment Terms names so that the Twinfield export configuration can be changed accordingly.

Failed to send "Invoice No" to Twinfield. The VAT on the detail lines is not equal to the VAT on the VAT lines.

Case 55540

No such property: Export for class: Script1 - Export Failed

Case 56265

GB is an invalid performance country, because it equals the country of the current company

Case 63468

Failed to send to Twinfield. The base amount (0.00) must be the sum of the detail lines (302) with the VAT-code P-EUREV. The base amount in the base currency (0.00) must be the sum of the detail lines in the base currency (270.05) with VAT-code P-EUREV. Invalid XML - 'performancetype' element may not be supplied. Invalid XML - 'performancecountry' element may not be supplied. Invalid XML - 'performancevatnumber' element may not be supplied.

Case 63468

Failed to send 0000000001 to Twinfield: transaction 1: header office: Company 78 does not exist.

Failed to send 0000000001 to Twinfield: transaction 1: line 1 dim2: There may only be one matchable dimension within an account code.

The value of Export.Twinfield.DetailLine.dim1.sales needs to be a code taken from Accounting, Dimensions, Profit and Loss in Twinfield. I changed it from EDU to '1555' and the error disappeared. If you don't specify a value for this setting it defaults to the client's nominal code, which is probably what they'll want to do when the system is live.

Failed to send 0000000001 to Twinfield: transaction 1: line 1 dim2: General ledger account Debtors with number 7010 requires specification of the relation or cost centre.

Failed to send SBCN0000000XXX to Twinfield: transaction 1: lines: The VAT on the detail lines (0.00) is not equal to the VAT on the VAT lines (-284.90).//Total VAT base value on detail lines (0.00) is not equal to total value on VAT lines (-284.90)

Case 75093

Case 84444

Item: 
SupplierInvoice: ID:xxxxxx, refCode:fbbc77e1-f81a-40b4-8051-1e9b38578107, reckoningNumber:Proforma 2491, documentDate:2017-03-17T00:00:00.000Z, salesTax:225.20, vat:225.20, salesTaxRate:20.00, net:1126.00, agencyId:10, created:2017-03-17T09:21:40.000Z, dmsReference:78958fa8-6997-4038-bb47-3a17056a3d38, ltdCoProviderId:1784, workerId:null, currency:GBP with 1 lines for Document label 
Error: 
Invalid XML data. (An error occurred while parsing EntityName. Line 1, position 88.) - Failed to send message to Twinfield

Case 84444

Error caused by the ampersand in the accounts ref of the provider. Change to be deployed.

Potentially multiple causes.

1. Populated Export.Twinfield.europeanSalesList = S-REVCHG-NOVAT and Export.Twinfield.zeroRateVATCodeList = S-REVCHG-NOVAT

Payroll employee update failed for Worker Name (Worker ID) Payroll response:

System.Web.Services.Protocols.soapException: The employee number 'Worker ID' already exists in the database for this company.

Reason 1

RSM InTime is set to be able to reuse the information against a user. This means that if they stop working for the agency and then return, the old details can be restored. This works by using the existing ID in RSM InTime but appending a number in InPay (where each spell a worker is at the agency needs a unique reference for reporting to the HMRC). Hence worker ABC in RSM InTime would be linked to ABC in InPay. Then if they went somewhere else and returned, you could reinstate them and they would appear as worker ABC still in RSM InTime but would then be worker ABC-1 in InPay. 

What has happened here is that a new version of the worker has been created in RSM InTime (not by the system) so that there is xxxxxxx and xxxxxxx-1 both for the same user in RSM InTime. The first of these has already been reinstated so that it was pointing to record xxxxxxx in InPay but now points to a new version xxxxxxx-1. The second worker in RSM InTime is treated as new and is trying to be created in InPay with that same reference. 

Support can update the InPay ref, for example as xxxxxxx-1-1. Any older versions of the worker will need to be tidied up. The new worker can be used in the meantime though. Log a call with Support.

Reason 2

The worker exists in both RSM InTime and InPay but for some reason the InPayID in RSM InTime does not exist. Log a call with Support who can check this for you.

Information! This worker is not currently linked to InPay

Case 55254

Case 57049

When re-instating a WorkerThe worker could not be re-instated: Failed to sync with InPay - Payroll employee update failed for Name Payroll response: Could not find code for in payroll Company Tables

Timesheet 210198: Worker Inpay ID is missing

Timesheet 210198: Failed to export because Worker has an invalid InPAY Account Number: null Worker Inpay ID is missing