Skip to main content

Abacus: Service Activity Import

In this article, we will explain whether Abacus can be used to import service activity for billing with a CSV file that includes header and detail records.

D
Written by David Bayley-Hamilton
Updated yesterday

Abacus has a process you can use to import service activity for billing. The process accepts a CSV file comprising two record types: a header record for each service user/week and, beneath this, one or more detail records against which actual service delivered is recorded.

Example CSV File

SERVICEACTIVITY, USER01, 16/10/2016, 20/07/1948, B90 1FJ
SERVICE, USER01, Home Care AM, 5, Prov0001
SERVICE, USER01, Home Care PM, 5, Prov0001
SERVICEACTIVITY, USER02, 16/10/2016, 12/03/1965, B93 8BM
SERVICE, USER02, Home Care AM, 12, Prov0003
​
​CSV File format
​

Field Name

Description

Format

Valid Values

Mandatory

RecordType

The type must always be specified thus to denote that this row represents service
user information.

Alpha numeric.
Uppercase

SERVICEACTIVITY

Yes

Reference

Unique reference by which the service user as known to the Council (Mosaic Person ID).

Alpha numeric.
Max 10 characters

Yes

WeekEnding

Date

Yes

DoB

Only required if additional validation if requested by customer.

Date

Postcode

Only required if additional validation if requested by customer.

Text

Field Name

Description

Format

Valid Values

Mandatory

RecordType

The type must always be specified thus to denote that this row represents service
user information.

Alpha numeric
Uppercase

SERVICE

Yes

Reference

Unique reference by which the service user as known to the Council (Mosaic Person ID).

Alpha numeric
Max 10 characters

Yes

Service

The name of billing service (Dom Service) or the Name of the Rate Category.

Text

Yes

Units

Number of units delivered or credited. For negative values the minus sign must be present before the numeric figure.

Decimal

Yes

ProviderRef

Unique reference for the supplier (Mosaic Organisation ID).

Text


If data for the same combination of service user / provider / billing service / week is sent on more than one occasion, e.g. in subsequent interface runs, one of two approaches is supported; a mixture of these approaches is not supported:

  • Only changes are sent on subsequent interface runs, i.e. a differential.

  • A complete set of data for the service user / provider / billing service / week is supplied each time, i.e. the net amount of units for the service user / provider / billing service / week.

Alternatively, you can send data for each service user/week just once, with any updates made manually in Abacus.

Did this answer your question?