Skip to content

+44 (0) 3453 40 30 40 (UK)

+353 (01) 6205 599 (IRE)

Yes, the Contract Ledger not only provides a detailed analysis of costs, broken down by resources and optionally operations, but all costs are identified as being outstanding or paid. We are therefore able to see in both enquiries and reports the detail of costs and cash paid per contract. This combined with cash received can immediately provide cash flow information.

Yes, our construction accounting software has a built-in information monitor, anything from account maintenance creation or modification through to monitoring bank balances can generate messages that appear as either onscreen prompts or they can be sent to the user via email or text message if away from the office.

Yes, our built in report writer allows for the consolidation of multiple companies even if they have differing nominal account structures.

Yes, the system is able to handle multiple currencies with reporting either in a base or local currency, additionally full Southern Irish VAT reporting and Subcontractor legislation is catered for.

All reports within the system can be run at anytime. The standard reports such as aged creditors and debtors are able to be run retrospectively. Reports from the system's report formatter are easy to create with all formatting being designed within an Excel environment.

If a user has access to a broadband connection they can use the system. Our Evolution systems have been designed specifically to allow for this type of environment. We recognise the need for company information to be protected, so all transmitted data is encrypted for security.

Our solution has a full Document Management module that allows for the storage of all reports and forms, there is no longer a need to print and file documents for internal use such as invoices, remittance advices, payslips, subcontractor certificates etc. A copy of the document is stored and available should a hard copy be required. In addition any document that is to be sent to a creditor, client, subcontractor, etc… can be emailed as an adobe© PDF file thereby avoiding printing and postage costs whilst protecting the environment.

See our Document Management section

Our Construction Accounting Payroll module allows for any payroll (weekly, monthly, directors) to be centralised. Any employee can be charged to multiple companies within the group for a period and where an employee is costed to contracts their costs including employers costs would be charged to the appropriate contract / company. Of course all the appropriate intercompany accounts are updated.

See our Construction Payroll section

Yes, our construction software enables businesses to submit their returns to the HMRC for online verification and monthly report filing avoiding the need for lengthy telephone calls and reporting. See Working with Subcontractors

Yes, the Subcontractor Ledger has a full authorisation of payment routine which allows for the recording of a Subcontractors Payment Certificate by a Surveyor or Contract Manager. This is passed to a manager for authorisation or rejection. If authorised the certificate passes to the accounts department for payment.

Yes, any Payment made from the system can be made via the BACS process, all payments from various sources can be grouped to form a single payment run.

Yes, providing your on-line banking allows for the downloading of a statement file, the system's reconciliation process can automatically match transactions of the same values with same reference, eg cheque number and with the transaction being within a specific date range. This greatly speeds up the reconciliation process leaving only sundry items for manual matching.

Yes, where an invoice is received and during processing it is found that no Goods Received Note (GRN) has been entered, the invoice can be processed as a “combined entry”. This has the effect of recording both the invoice and the delivery at the same time. The invoice can also be given a held status until delivery of the goods has been confirmed.

Yes, the Purchase Ledger payment routine is both simple and efficient. Firstly the system will prompt with all items that are due for payment to a due date. The operator can then either accept the values shown or drill down to each transaction choosing whether or not to pay or part pay. If the system's document management system is in use the operator can also see an image of the original transaction during the payment process.

As part of the original specification of the system the Nominal and Contract Ledgers were seen to be the hub of the financial systems. With any transaction being costed to a contract the Nominal code to be updated is deduced from a combination of the Contract and the costing analysis. The Nominal Accounts that are updated from the Contract Ledger are marked as “Cost Only” preventing any entry that has not originated from the Contract Ledger. This ensures total integrity of the two ledgers.

All Contract Sales transactions are defined and created to an individual company’s requirements. The flexible configuration tools enable the system to cater for all types of transactions not only Application, Certificate, Invoice and Payment but also transactions such as Internal Valuation, WIP etc. Transactions are created as tax point invoice or tax point cash with input being cumulative or movement.

Our system has been developed using Open Server technology enabling operation on a wide variety of platforms including Windows Server Family and Unix. The software embraces Client Server technology using TCP/IP and includes encryption & compression as standard. See Technical Consultancy

The system was designed from the outset to operate with any industry standard ODBC standard database (SQL Server, Oracle, MySql etc). This design means that the application needs no knowledge of the database being used; this is all performed by the data tier. Different tables can even reside in multiple databases. The system provides standard data handling functionality independent of the database being used, this includes comprehensive record locking, individual company restores and XML data import/export.

Our product has been created to use wide area network (WAN) environments, meaning it operates over standard Internet broadband connections saving large sums in network costs. The system will run remotely via a secure RDP connection. All data passing over the network is automatically encrypted and compressed, meaning that your information is safe.

All windows can be sized to meet the resolution of your screen. With today's ever increasing screen resolutions this is an essential feature in modern software to ensure user comfort and efficiency. Each user’s preferences are stored at their desktop.

Our Evolution packages a true windows based application. The user interface has been designed specifically to integrate with the latest Microsoft Suite including Excel, Word and Outlook.

Our Evolution M product is designed with an XML Interface to all Posting Routines which allows for integration with 3rd party packages including most estimating solutions (Conquest, Estimate, Causeway etc…) and Workspace from Union Square.

Yes, we have developed tools that can be used for the transfer of data from other systems or allow integration with estimating and other third party products. See Data Conversion & Migration

Evolution M is designed with an XML Interface to all Posting Routines which allows for integration with 3rd party packages including most estimating solutions.

Yes, our construction management software has a built-in information monitor, anything from account maintenance, creation or modification, through to monitoring bank balances can generate messages.

Yes, the Contract Ledger not only provides a detailed analysis of costs, broken down by resources / operations, but all costs are identified as being outstanding or paid. We are therefore able to see in both enquiries and reports the detail of costs and cash paid per contract. Combined with cash received this can immediately provide cash flow information.

Using RTI, employers and pension providers will tell HM Revenue & Customs (HMRC) about tax, National Insurance contributions (NICs) and other deductions when or before the payments are made, instead of waiting until after the end of the tax year.

RTI will:

  • Make the PAYE process simpler and less burdensome for employers and HMRC for example, by removing the need for the end of year return (forms P35 and P14) and simplifying the employee starting and leaving processes
  • Make PAYE more accurate for individuals, over time reducing the number of bills and repayments sent after the end of the tax year
  • Enable HMRC to pursue late payments more effectively
  • Support the payment of Universal Credit
  • Reduce Tax Credits error and fraud

Employers and pension providers will send this information to HMRC online for payments made to all their employees, including those paid below the National Insurance Lower Earnings Limit (LEL).

No - it is for the operation of PAYE only.

No - end of year returns (forms P35 and P14) or P38A supplementary return will not be needed as employers will tell HMRC about all payments made during the tax year each time their payroll is run.

The hours worked is required for the purposes of calculating Tax Credit payments.

Once the EAS has been successfully submitted the employer is considered to have joined RTI. The EAS should be submitted at least 24 hours before the first FPS.

If you have claimed an advance of statutory payments then the amount you report on an EPS will be set off against the PAYE due as reported on an FPS. If a credit remains this will be set-off against any advance you have claimed, and any remaining credit will be used against any other amount due, or if nothing is due you can contact HMRC and claim a repayment or reallocation.

If you are registered with HMRC as an employer who pays HMRC quarterly, we will know to expect quarterly payments from you without you needing to do anything further.

All employers need to send an FPS every time they pay their employees, whether they pay HMRC monthly or quarterly. If you haven't made any payments to any employees in a tax month, you should send HMRC an EPS showing 'No payment due as no employees or subcontractors paid in this pay period' within 14 days following the end of the tax month. This also applies to employers who pay HMRC on a quarterly basis - if you do not, then HMRC will specify an amount due for that month, and pursue this at the end of the relevant quarter.

Yes. You can submit one EPS to advise us of your 'period of inactivity'. HMRC will not expect any other return, nor any payment, for the period(s) reported.

The system will count the two employments as separate by operating on the information submitted by the employer. The last payment from the first employment should have a date of leaving.

The first payment from the new employment should include the starting information including start date and should not take into account pay and tax information from the previous contract of employment when calculating the year to date figures. If the employer is using payroll IDs they must ensure the second contract is set up using a different payroll ID, i.e. employee number.

Employers and pension providers will be required to report PAYE information (via an FPS or EPS) in real time 'on or before' payment is made to employees or pensioners for the vast majority of payments that they make.  

Assuming that the five positions are treated as separate employments and tax and National Insurance are calculated separately for each employment, as each finishes a leaving date should be sent as part of the relevant FPS. HMRC will, if necessary, issue a code each time.

If the earnings from all five jobs are accumulated and tax and National Insurance are calculated as one employment (i.e. there is one tax code in operation) no additional action needs to be taken until the last employment ceases.

The EYU is needed to correct details of previous RTI years - you will only be able to use it for the tax years where you were required to operate PAYE using RTI. An FPS can only be sent up until 19th April following the end of a tax year - after this any corrections need to be made on an EYU.

Non-RTI years will still be corrected via amended P35/P14s as per the existing PAYE arrangement.
 

Adjustments can be made throughout the year with the final FPS showing the correct Year-To-Date (YTD) figures. If adjustments relate to previous RTI tax years then the EYU is needed to show the correct details.

Yes you can have a refund at the year end, and if there are no outstanding debts. 

The date to enter is the date the employment ended. The exact date of this is for the employer to decide.

The following will remain unchanged:

  • PAYE - PAYE remains the same using RTI. It is only the reporting that changes.
  • Coding notices - using RTI employers will still be able to choose how they receive coding notices; as they do now.
  • Reporting a change to HMRC e.g. updating employee's new name or addresses for HMRC records - an RTI submission will not update HMRC records. It remains the responsibility of the individual employee to notify HMRC of changes of name, address, etc.
  • HMRC messages to employers using RTI - HMRC will continue to use the Data Provisioning Service (DPS) and EDI outbound message services.
  • Payment dates using RTI - payment dates to HMRC will remain the same using RTI.
  • Forms P60 - P60s will remain using RTI.
  • Forms P11D - HMRC are not planning to change the requirement to complete a deductions working sheet (or electronic equivalent)

RTI is not changing the existing CIS process. Employers will continue to complete and file monthly returns due under the existing CIS arrangements.

Evolution will allow for the National Insurance number field to be left blank if the National Insurance number is not known, but you must provide the employee's address. However where possible, you should ensure that you obtain the correct National Insurance number for your payroll records.

You should not use a default date of birth. You should make every effort to obtain the correct date of birth for the individual, especially for new pensions coming into payment. Where, despite these efforts, it's not been possible to obtain the correct details, please continue to use the date of birth currently held on the payroll.

HMRC will attempt to validate National Insurance numbers provided by checking with the DWP. In cases where there is a discrepancy, or where the employer has not provided a National Insurance number, HMRC will inform the employer.

If the annuitant (a person who is entitled to receive benefits from an annuity) queries the National Insurance number provided by HMRC, the annuitant should contact HMRC to resolve the query.

The more accurate and comprehensive employee data the employer gathers and maintains, the more likely it is that the National Insurance number provided will be correct.

The passport number will only have to be provided if the employer or pension provider collect it as part of their checks that the employee or pension recipient is entitled to work in the UK or receive a UK based pension.

It has always been important to make sure the information that you send HMRC about your employees is accurate to help ensure that your employees pay the correct Income Tax and NICs. Improving the accuracy of the information you hold and send to HMRC will help match the information to the correct HMRC record. This could save you money by helping to reduce the number of employee enquiries you receive.

This is not just important for tax and NICs. From October 2013, RTI will support Universal Credit by providing the DWP (Department for Work and Pensions, formerly the Benefits Agency) with up to date information about claimants' employment income. Ensuring your employee information is correct will help to ensure they receive the right amount of credit.

As part of the process for an employer joining RTI, HMRC will align the records of employees held on the NPS system (National Insurance and PAYE Service, is a single national computer system introduced by HMRC in July to replace the 12 regional databases that previously handled PAYE processing) and the records held by employers.

In the meantime HMRC recommends that you start to prepare for RTI by checking the information you hold.