PL_JPK_KR_PD - Dziennik Fields and Default Mapping
The Dziennik section includes a detailed list of all journal entries and posting transactions relevant to the reporting period. Each entry provides information such as account, amount, reference, and type. It reflects the general ledger movement within the defined period.
This section is generated based on a dataset defined in the Poland Localization Settings → JPK_KR_PD → JPK_KR_PD Dziennik Dataset ID.
Below is the standard mapping based on the default dataset:
Field Name | Field Description | Default Mapping | Default Mapping Description | Notes & Compliance Guidance |
|---|---|---|---|---|
D_1 | Sequential journal number formatted like “1/Zak/01/2025” | {custbody_sta_pl_gaplessnumber} | Displays the gapless number per journal type. | Example format: 1/Zak/01/2025 Create a gapless, human-readable journal number per journal type. Often used for auditing. By default, this is mapped to Staria’s Poland Localization gapless numbering system. If you are using your own gapless numbering setup, you must update the mapping accordingly. Create a custom version of the dataset in NetSuite, and assign this custom dataset in the Poland Localization Settings. If your existing transactions do not currently use any gapless numbering system, you should review this requirement and plan how to implement it to ensure compliance. |
D_2 | Journal description like “Purchase” or “Sales” |
| Displays the name of the journal type selected in the new custom field on the transaction record. | Examples: Purchase, Sales, General Journal. If you are using your own Journal Type configuration, update the mapping to reflect your setup. Create a custom version of the dataset in NetSuite and assign it in the Poland Localization Settings. If your existing transactions do not currently use any Journal Type field, review this requirement and plan for its implementation to ensure compliance. |
D_3 | Unique counterparty (customer/vendor) ID |
| Uses the line-level entity ID if available, otherwise the header-level one. |
|
D_4 | Document number assigned by the issuer |
| Displays the internal transaction number (e.g., invoice number). | Uses the transaction number, e.g., invoice number: F-10023/07/2025. |
D_5 | Type of accounting document (e.g. invoice, receipt) |
| Displays the label or name of the accounting document type selected from the new custom field on the transaction. | Examples: Invoice, Cash Receipt, Credit Note. If you are using your own Accounting Evidence Type configuration, update the mapping to reflect your setup. Create a custom version of the dataset in NetSuite and assign it in the Poland Localization Settings. If your existing transactions do not currently use any Accounting Evidence Type field, review this requirement and plan for its implementation to ensure compliance. |
D_6 | Date the business transaction happened |
| Converts transaction date to YYYY-MM-DD format. | Represents the economic event date. Should reflect when goods/services were delivered. |
D_7 | Date the accounting document was prepared |
| Converts document creation date to YYYY-MM-DD format. | When the transaction was entered into NetSuite. |
D_8 | Date entry was recorded in the books |
| Converts journal posting date to YYYY-MM-DD format. | Useful for identifying timing differences between creation and posting. |
D_9 | Name of the person responsible for the entry |
| Shows the next approver’s name, or the creator if not approved yet. |
|
D_10 | Business transaction description (max 512 chars) |
| Uses the line memo if present, otherwise the header memo. | Prefer line-level memo for more accuracy. Example: Invoice for order #7894 - July supplies. |
D_11 | Amount of the transaction (PLN) |
| Retrieves value from custom linked record field. |
|
D_12 | Invoice number from KSeF (if applicable) |
| Displays the KSeF invoice number if the invoice was issued through the KSeF system. This field will only populate correctly if the new KSeF feature is implemented alongside the JPK_KR_PD report. If a different solution is used for KSeF integration, this field must be remapped to the appropriate source field accordingly. | Available only if KSeF integration is enabled. If you're using a different solution, remap this field accordingly. |
Z_1 | Entry line sequence number |
| Converts the line number to text, starts from 1. | Used to sequence lines within each journal entry. Starts from 1. |
Z_2 | Entry line description |
| Shows memo at line level if available, or header memo. | Recommended to use descriptive memos, e.g., Raw materials for PO#1234. |
Z_3 | Final G/L account name/number |
| Displays the name or number of the account affected. | Make sure G/L account names follow a clear naming convention for audit readiness. |
Z_4 | Debit amount |
| Converts the debit amount to text. |
|
Z_5 | Debit amount in foreign currency (if applicable) |
| If currency isn’t PLN and there’s a debit amount, show the foreign currency value. |
|
Z_6 | Foreign currency code for debit (optional) |
| Shows the foreign currency (e.g., USD) used for the debit if not PLN. |
|
Z_7 | Credit amount |
| Converts the credit amount to text. |
|
Z_8 | Credit amount in foreign currency (if applicable) |
| Shows the foreign currency amount (positive value) for credit if currency ≠ PLN. |
|
Z_9 | Foreign currency code for credit (optional) |
| Displays the foreign currency used for the credit amount if not PLN. |
|
©2024 Staria. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher.