Skip to main content
GullySystem
Business Services · Data Processing Firm Management Software

Client batches, keying packets, error checks and delivery files in one record.

Manage client batches, keying instruction sheets, work packets, double keying, accuracy sampling, delivery files and billing in one system. Each batch carries its intake count, its keyers and its error record from the courier’s drop to the invoice. The floor sees its own packets, the checker sees errors by field, and the client sees only its own work.

  • Client field lists, keying rules and delivery layouts entered as you work today
  • Open batches, keyer lists and client rate cards migrated
  • Changes to layouts and rate cards made by GullySystem staff on request

Data Processing Firm Management Software covers batch receipt, keying packets, verification and delivery files for bureaus and in-house teams, with GullySystem building the client layouts and rules. Each batch holds the client’s count, the packets cut from it, keyer output, field-level error rates and the reconciled delivery file. Invoices follow records delivered against each client’s rate card.

Where it breaks today

What goes wrong before the software.

Intake counts do not match output

A client states a count of forms, and the floor keys a different number. Short cartons, torn pages and duplicate sheets are noticed late, if at all, and the gap turns into a dispute over the invoice.

Keying rules sit on loose sheets

Every client wants different field lists, date formats and ways of coding a blank field, so each one gets a separate instruction sheet lying around the keying floor. When a rule changes, some keyers use the old sheet. The error surfaces only when the client returns the file.

Error rates hide the field that fails

A batch-level percentage says little. The postcode field may fail often while names are clean. Without counts by field and keyer, retraining targets the wrong people.

Packets are handed out from a whiteboard

Supervisors write packet numbers beside keyer names. A rejected packet is rubbed out and rewritten, and by afternoon nobody can say which packets are with whom.

Piece-rate pay is counted by hand

Output is counted per keyer in thousands of keystrokes or records, then reduced for rejected work. The calculation takes the accounts clerk a day and is disputed every month.

Client data moves too freely

Scans and exports sit in shared folders that every keyer can open. When a client asks who handled its medical or financial forms, the answer is a guess.

How it runs

How the work flows through it, step by step.

  1. 1

    Receipt

    A batch arrives by courier, upload or secure transfer. The intake clerk counts cartons, pages or files, notes damage, and logs it against the client, the job type and the date promised.

  2. 2

    Instruction sheet and packets

    The batch is tied to the current keying instruction sheet. A supervisor cuts it into packets of a few hundred records and assigns them to keyers by skill and workload.

  3. 3

    Keying

    Keyers open their packets and enter records against the sheet. Every packet shows its start, finish and record count. A second keyer re-enters the same packet where double keying applies.

  4. 4

    Verification

    A checker compares the two keyings or reads a sample, and errors are logged by field and by keyer. A packet over the error limit goes back for rework.

  5. 5

    Delivery

    Accepted packets are merged into the client’s layout. The record count is reconciled with intake, rejects and exceptions, and the file is released through the agreed channel.

  6. 6

    Billing and pay

    Records delivered are priced from the client’s rate card, and keyer tallies are summed for payroll. Rework done at the firm’s cost is shown beside the invoice.

Modules

What is inside.

Every module can be switched on, left out or changed to match how your team already works.

Batch receipt and intake count

Log each batch with client, carton or file count, damaged pages and promised date. The clerk signs off the count before any packet is cut, and shortfalls are raised with the client at once.

Keying instruction sheets

Hold each client’s field list, formats and blank-field rules as numbered versions. Keyers see the current sheet for their batch, and an older version stays on file for any batch already keyed under it.

Work packets and keyer assignment

Cut a batch into packets and give them to keyers and verifiers. See which packets are open, in progress, rejected or accepted, and who holds each one.

Double keying and field sampling

Compare two independent keyings or sample a share of records. Count errors by field, by keyer and by batch against thresholds set per client.

Rework and rejected packets

Return a rejected packet to the keyer who made it, with the faulty fields marked. Rework time is recorded separately, so the firm knows what quality costs on each client.

Delivery files and reconciliation

Build the output file in each client’s layout, with field order, separators and file naming. Reconcile its count with intake and exceptions before release.

Shift attendance and piece-rate pay

Mark attendance by shift and count records or keystrokes per keyer. Subtract rejected work and pass payroll a pay total that matches the packets.

Client rate cards and billing

Price invoices from records delivered, using each client’s rate per thousand records, per field or per page, with extra passes and rush batches added as contracted.

Turnaround board and due dates

Show every open batch against its promised date, with unassigned, in-progress and rejected packets counted. The supervisor sees a risk before the client does.

Client access and batch security

Give keyers access only to the batches they are assigned and give clients a view of their own work. Opens, downloads and exports are logged by person.

Solutions inside

The business modules it is built from.

Each one is also available on its own, or inside a system built for you.

  • Document Management

    Each client’s field list and blank-field rules are held as numbered versions, and every batch records which sheet it was keyed under.

  • Task Management

    A batch is cut into packets, each assigned to a keyer or verifier and tracked from open through rework to accepted.

  • Quality Control

    Two blind keyings or a sample of records are compared, and errors are counted by field and keyer against each client’s limit.

  • Attendance & Time Tracking

    Shift attendance and record counts per keyer feed a pay total, reduced by rejected work and matched to the packets.

  • Invoice Management

    Invoices are priced from records delivered against each client’s rate per thousand records or per page, including rush batches and extra passes.

  • Dashboards and KPIs

    Open batches sit beside their promised dates, with unassigned and rejected packets counted so a late file is visible earlier.

  • Roles and Permissions

    Keyers open only the batches given to them, while a client portal view shows its own batches and nobody else’s.

  • Audit Trail

    Every open, edit, download and export of client records is written against a named person, which answers a client’s question about who handled its forms.

Services

How we would put it in.

Setup, data migration, integrations and anything built on top.

Who uses it

One system, each person sees their part.

For the intake desk

Receive batches, check counts, note damage and log the keying sheet version. Raise shortfalls with the client before keying starts.

For floor supervisors

Cut packets, assign keyers and watch the turnaround board. Move work between shifts when a batch looks late.

For keyers and verifiers

Open assigned packets, key or compare records, and see their own output and rejected fields at the end of each shift.

For quality checkers

Run field sampling, record errors and decide whether a packet passes. Report which fields and keyers need retraining.

For account managers and owners

Read volumes by client, error rates, rework cost, late batches and unbilled deliveries without asking the floor for a count.

Reports

The numbers the owner asks for.

  • Batches received, in progress and delivered, by client
  • Intake count against records delivered, with exceptions
  • Error rate by field, keyer and keying instruction sheet
  • Rejected packets and rework time by client
  • Output per keyer per shift, before and after rejects
  • Batches at risk of missing the promised date
  • Records delivered and billed, by rate card
Good fit

Who this is built for.

  • Data entry and form-keying bureaus that serve insurers, banks and survey firms
  • Firms that digitise archives of invoices, claims or registers from scanned images
  • Processing teams that clean and reformat client exports before returning them
  • Subcontract keying centres that pay keyers per record or per thousand keystrokes
  • In-house back offices that run batches for several internal departments
Honest answer

When it is not the right choice.

  • One freelancer keying a handful of files each week gets by with a spreadsheet and a shared folder, so this system would add little.
  • Firms whose main work is answering calls and chats will find Customer Support Centre Management Software closer.
Made to fit

Adapted to your business before it goes live.

You are not handed a login and left to it. The product is set up around your records, your people and the tools you already use.

Client field lists and rules

Fields, formats, validation rules and blank-field codes are entered for each client the way their sheet states them.

Accuracy thresholds

The sample size, double-keying cases and error limits that fail a packet are set per client and job type.

Delivery layouts

Output formats, field order and file naming match what each client expects, including secure transfer routes you already use.

Pay and billing rules

Piece-rate formulas, shift allowances and the client rate cards are entered as you apply them today.

Existing batches and rosters

Before go-live, the intake desk imports open batches, keyer lists and client records from the tracker or sheets you keep now, then checks a few against the originals.

Hosted by GullySystem

GullySystem hosts the system, so intake, floor and billing work from the same records. Data protection terms in client contracts are reviewed with you at set-up.

Works alongside

  • Email
  • SMS
  • Secure file transfer
  • Document scanner folders
  • Accounting export
  • Spreadsheet import
Common questions

Questions owners ask before a demo.

Does it key the data itself?

No. Keyers or your own capture tool produce the records. The system assigns packets, compares keyings, counts errors and builds the delivery file from accepted work.

Can two keyers enter the same packet blind?

Yes. Each keyer enters the packet without seeing the other’s work, and mismatches are listed by field for a checker to settle. Which jobs use double keying is your decision.

How are field-level error rates counted?

The checker marks each wrong field against the source image. Counts roll up by field, keyer, packet and batch, using the thresholds you set for that client.

Can clients see the progress of their batches?

Yes, if you choose. A client can open a view of its own batches showing received count, packets done and expected delivery date. It cannot see other clients or keyer names.

Can we run different instruction sheets for the same client?

Yes. A client can have one sheet per job type, such as claims forms and enrolment forms. Each sheet is versioned, and each batch records which version it was keyed under.

How is confidential client data protected?

Access follows assignment, so a keyer sees only the packets given to them, and every open and export is written to a log. Retention and deletion terms are agreed with you for each client.

Can keyer pay be calculated from the output?

Yes. Records or keystrokes per keyer per shift, less rejected work, produce a pay total for payroll. The formula follows your own piece-rate rules and is set up with your accounts staff.

Can existing batches and client sheets be loaded?

Yes. Open batches, client field lists and rate cards are imported from your tracker or workbook. The intake desk checks a sample before the floor starts using it.

What does it cost?

The cost depends on keyer headcount, the number of client accounts and the count of delivery layouts to build. A working demo on your own batch comes first, and the quote follows in writing.

Wondering what it would cost? Share your requirements and an engineer will come back with a scope.

Book a demo

See Data Processing Firm Management Software with your own data.

Tell us how you run things today. We’ll show you the parts that matter to you and say plainly what would need changing.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements