For the complete documentation index, see llms.txt. This page is also available as Markdown.

Paid Reserves Opening Balances Template

The Paid Reserve opening balances template lets you import your paid reserves directly into the Paid Reserve Journal, where they can be posted.

Before you start

  • Understanding the Configuration Worksheet: Configuration Worksheet.

  • Understanding Excel templates: Excel Template Data Migration.

  • Items & Customers must exist.

  • Inventory Posting Setup must be set up.

The template is a pre-formatted spreadsheet with the fields you need to create your opening inventory paid reserve balances within Bevica.

You will need to prepare your Paid Reserve records by: Customer / Item / Location / Duty Status / Unit of Measure.

If Paid Reserves within this grouping have different condition, provenance, rotation number, etc., you may want to split those into multiple lines and assign each line its correct details.

The template has the following fields:

Field ID / Name
Related Table
FieldType
Note

1 Journal Template Name

(82) Item Journal Template

Code 20 (Mandatory)

Set to PRSTD. Any value entered here must already exist in its related table.

41 Journal Batch Name

(233) Item Journal Batch

Code 10 (Mandatory)

Set to Z_DATA MIG. Any value entered here must already exist in its related table. For large datasets, it is advised the Commit Per Line tickbox is enabled.

2 Line No.

Integer (Mandatory)

Must be a unique number per line. Line numbers normally start with 10000 and increment by 10000, for example 10000, 20000, 30000.

4 Posting Date

Date (Mandatory)

Enter a date here, typically the day before the go-live date.

34 Source No.

Code 20 (Mandatory)

The No. for the customer that owns the paid reserve. Any value entered here must already exist in its related table.

3 Item No.

(27) Item

Code 20 (Mandatory)

Any value entered here must already exist in its related table.

9 Location Code

(14) Location

Code 10 (Mandatory)

Any value entered here must already exist in its related table.

5402 Variant Code

5401 Item Variant

Code 10 (Mandatory)

Enter either DUTY PAID or DUTY FREE. Any value entered here must already exist in its related table.

5407 Unit of Measure Code

5404 Item Unit of Measure

Code 10 (Mandatory)

Any value entered here must already exist in its related table.

13 Quantity

Decimal (Mandatory)

The quantity in the Unit of Measure.

16 Unit Price

Decimal (Mandatory)

The Price the customer paid for the stock in local currency. This may be used later to calculate VAT.

7 Document No.

Code 20

An internal reference.

60 Document Date

Date

An internal reference.

51 Provenance/Source

Text 100

An internal reference.

52 Condition

Text 100

An internal reference.

62 External Document No.

Text 35

An internal reference.

58 Internal Information

Text 100

An internal reference.

200 Rotation No.

Code 20

An internal reference.

230 Rotation Ref.

Code 20

An internal reference.

Upload the journal

Once the template has been applied, navigate to the Paid Reserve Journal batch and check that the journal holds the same information as the data migration template used.

  • Ensure all columns you have imported data into are visible.

  • Have all the lines been imported?

  • Select a number of lines at random, are they all correct and Total Price calculated correctly.

  • You may want to export the journal lines to Excel and make sure the total quantities and amounts are what you expect.

Post the journal

Before posting any opening balances, it is a good idea to copy the company as a backup, so you have a point to return to if there are problems once the Paid Reserve Journal has been posted. See Bevica Select - Creating new Bevica companies for information on how to do this.

Reconcile

Once Posted, the entries need to be reconciled with the values from your old system and Bevica. The following should be checked:

  • Quantity by Item/Customer (by Location, Variant, Unit of Measure)

  • Value by Item/Customer (by Location, Variant, Unit of Measure)

Another trusted user, rather than the person who created and posted the opening balance, should perform these checks. They should do this using their own data source from your previous system and not rely on the migration files you used in case there were errors on those.

Last updated

Was this helpful?