Dealer Vehicle Registration Operations in Poland – From Registration Pack to Customer Handover
Firma świadczy usługi w zakresie akcyz, rejestracji samochodów i ubezpieczenia. Profesjonalne doradztwo i szybka obsługa.
Zadzwoń do nas
Napisz do nas
kontakt@akcyzawarszawa.pl
Zostaw dokumenty od twojego auta ekspertom - Akcyza warszawa
O Firmie
Właściciel serwisu: Mariola Ślęczkowska
REGON: 141314025
NIP: 4960058650
Adres biura
Aleja krakowska 157 02-180 Warszawa
A car can be washed, fuelled, photographed for the handover and standing in the delivery bay, and still be unavailable to the customer. The registration file is open, the plates are at the office, the leasing company's authorisation arrived in the wrong name, or the insurance starts on Monday. None of that is visible from the sales system, which shows the vehicle as ready.
This guide is written for the people who own that gap: dealer operations and registration managers, customer delivery teams, dealer network and importer operations, back-office and shared service centres, and fleet sales departments delivering 40 vehicles to one corporate customer on one date.
It covers what belongs in a registration pack, why owner, buyer, user and applicant are four separate fields, how salon registration through e-Doręczenia works now that it is the electronic route, how authorisation behaves at volume, how plates and temporary permits should be tracked as physical assets, and why the case does not close when the plates arrive.
Key points
- An authorised representative of the sales showroom where the vehicle was bought may file the registration application for the buyer. The dealer needs a written authorisation from the owner, or from a representative of the company that owns the vehicle, and a company e-Doręczenia mailbox.
- Since 1 January 2026 this matter is handled electronically only through e-Doręczenia. A dealership without a working company mailbox has no electronic route.
- Stamp duty on a power of attorney is PLN 17 per authorisation relationship, charged separately for each proceeding in which the document is filed. At 500 deliveries a month it is a predictable per-VIN cost line.
- Competence follows the owner's residence or registered seat, not the dealership's address. For a corporate or leasing buyer, that means the office is determined by the buyer's data, which the dealer holds and frequently gets wrong.
- On acceptance of the application the office issues a temporary permit and plates; the permanent registration certificate is collected afterwards. The registration case does not close when the plates arrive.
- Where a vehicle brought in from another EU state is sold before the registration deadline expires, the seller ceases to be the owner and the obligation passes to the buyer. For dealer stock sold inside the window, this matters.
Registered is not the same as customer-handover ready
Registration complete and customer-handover ready are not the same status. A vehicle may have plates and still be blocked by insurance, owner documentation or an internal release control.
Legal registration status is what the authority has decided. Delivery readiness is a dealer condition made up of several things, most of which are not legal requirements at all: plates physically at the site, the temporary permit matched to the VIN, insurance in force from the handover date, the customer's or lessee's paperwork complete, the dealer system updated with the registration number, and delivery authorised internally.
Keeping these apart in reporting matters because they fail for different reasons and different people fix them. A delivery board that shows only "registered / not registered" cannot tell a sales manager whether tomorrow's handover is real.
Useful status stages, in order:
Vehicle physically ready → document-ready → registration-ready → registered → insured → handover-ready
Customer delivery should be planned from registration readiness, not from the date the vehicle physically arrives at the dealership. That single sequencing change removes most handover failures.
Control the process by VIN
The VIN should be the primary key of the dealer registration process. It is the only identifier that exists consistently from allocation through plates, insurance, handover and permanent certificate collection.
Everything else moves. Order numbers change on reconfiguration. Customers change, and so do their legal entities. A retail sale becomes a leasing transaction three days before delivery, which changes the owner. Dealer stock IDs do not always survive reassignment between branches. And the registration number, the identifier everyone naturally reaches for, does not exist during most of the work.
The VIN connects the vehicle to the customer, the owner, the certificate of conformity, the tax position, the registration application, the plates, the insurance policy, the delivery record and the permanent certificate. Any field in the process that cannot be joined back to a VIN is a reconciliation problem waiting for month end.
Owner, buyer, user, applicant
Four roles, and in dealer operations they separate constantly.
In a private retail sale the buyer, owner and user are the same person, and the dealer is an authorised representative in the procedure. In a corporate purchase the company is the owner and an employee is the user, which changes whose data goes into the application and who signs the authorisation. In leasing the leasing company is the owner, the customer is the lessee and user, and the dealer supplies the vehicle without ever owning the registration relationship. In rental and mobility sales the fleet operator or a financing party may own while the operator uses.
With a foreign buyer the ownership and representation structure has to be established before anything is promised.
Most dealer registration errors are role errors before they are document errors. The invoice names one party, the authorisation is signed by another, the application is filed with the data of a third, and the office returns the file. The fix is structural: owner, buyer, user and applicant are four separate mandatory fields on the vehicle record, filled per VIN, never inherited from the sales note.
What belongs in the registration pack
The pack is per VIN and its contents depend on the vehicle and the transaction. It is worth separating a standard new-vehicle pack from an exception pack, because treating every delivery as a potential exception slows the 90% that are not.
Standard new vehicle, Polish stock, retail or corporate buyer: the invoice or other ownership document, the certificate of conformity, evidence of the vehicle's tax position, the customer's or company's identification data, and the signed authorisation.
Exception packs add, depending on the case: leasing company authorisation and corporate documents, foreign company representation documents, the foreign registration certificate and ownership chain for imported units, customs documentation for non-EU vehicles, technical inspection evidence where required, sworn translations, and final-stage documentation for converted or bodybuilt vehicles.
Two items deserve specific attention because they are the ones dealer teams most often assume.
The tax evidence is not one document. Depending on the vehicle it is confirmation that excise was paid, a tax-office document confirming there is no obligation to pay it, or a certificate confirming exemption for an electric or hydrogen car. Each is obtained per vehicle. An EV that owes nothing still needs its certificate in the file, and where the dealer sells a car not previously registered in Poland, the seller is obliged to pass that certificate to the buyer. Make it a delivery item in the supply chain rather than a discovery at submission.
The certificate of conformity has to match the VIN in front of you. On standard stock it does. On a vehicle reassigned between branches, on a converted van, or on a unit that arrived through a non-standard route, it is worth checking rather than assuming. Where a vehicle was completed in stages by a bodybuilder, the document covering the chassis is not the document covering the finished vehicle, which is covered on our page on multi-stage vehicle registration.
Customer data is a registration input, not a CRM field
Small commercial-data errors become registration blockers, and they arrive from the sales side.
The recurring ones: a trading name used instead of the registered company name, an old address after a move, outdated company register details, an incorrect personal identification number, a signature from someone no longer authorised to represent the company, leasing company details taken from a previous transaction, a mismatch between the invoice and the party that will actually be the registered owner, and a customer that changes its legal entity between order and delivery.
The office reads documents, not intentions. A customer who is commercially the same company but legally a different entity from the one on the invoice is a new case, not a correction.
The practical control is a verification step at order confirmation rather than at submission: company data checked against the register, personal data checked against an identity document, and the leasing company's own data supplied by the lessor rather than reconstructed by the dealer.
Authorisation at volume
A dealer acts in the procedure on the strength of an authorisation, and at network scale the handling of that document is a process in itself.
Three things are worth knowing.
The stamp duty is charged per proceeding. The fee is PLN 17 per authorisation relationship, and where one standing authorisation is filed before the same authority in several proceedings, the charge applies separately to each. A general authorisation removes the signing and courier burden, not the cost. Budget it per VIN and reconcile it monthly.
Who signs has to be verified, not assumed. For a corporate buyer or a leasing owner, the signatory must be entitled to represent that entity as disclosed in its register. A board change at a large leasing partner quietly invalidates a template that worked all quarter.
Format consistency is an operational asset. Networks that use one authorisation template with a fixed scope, a fixed signatory list and a fixed way of identifying the vehicle get predictable throughput. Networks where every branch drafts its own spend their week on counter-level refusals that have nothing to do with the vehicles.
Registration through the sales showroom, and e-Doręczenia
Poland has a dedicated route for exactly this situation. An authorised representative of the showroom where the vehicle was purchased may file the registration application on behalf of the buyer. It requires two things: a written authorisation from the owner or from a representative of the company that owns the vehicle, and a company e-Doręczenia mailbox on the dealer's side.
Since 1 January 2026, this matter is handled electronically only through e-Doręczenia. ePUAP no longer serves as the general channel. In practice that turns an IT and administrative prerequisite into a commercial one: a dealership without a working company mailbox, with named users and a signature method in place, does not have the electronic route available to it at all.
Two details that decide whether the route actually shortens delivery times.
The authorisation has to cover collection, not just filing. The representative should be authorised to receive the temporary registration decision, the temporary permit and the legalised plates, not only to submit the application. An authorisation drafted for submission alone produces a file that completes and then stops.
Notifications arrive electronically. Information that documents are ready for collection comes through the same channel, which means somebody has to be watching the mailbox daily. A shared mailbox nobody owns is the digital version of an unopened envelope.
Further changes extending fully electronic registration have been moving through the legislative process, so a dealer network building a workflow now should confirm the current state of the rules before fixing its process in software.
Which office, and why it is not yours
Competence follows the owner's place of residence or registered seat. For a dealer this is counter-intuitive: the vehicle is at your site, your staff prepare the file, and the case belongs to the authority competent for somebody else.
The consequences at network scale are practical. A dealership in one city routinely files in several offices, each with its own service arrangements. An entity with separated organisational units may be able to register through the authority competent for the seat of that unit, on the application of its authorised head, which matters for corporate and leasing buyers with branch structures. And where the vehicle is entrusted by a foreign legal person to a Polish entity, the case goes to the authority competent for the Polish entity's seat on the basis of a document confirming the entrustment.
Determine the authority from the owner's data at order confirmation, not at submission. It affects lead time, courier routing, who physically goes where, and what the delivery date can honestly be.
Plates and temporary permits are physical assets
When the application is accepted, the office issues a temporary permit and plates, and the permanent registration certificate follows later. For a dealer that is genuinely useful: the customer can take delivery without waiting for the final document.
It also introduces physical objects into a process that dealer systems tend to treat as pure status. Plates have to be tracked as inventory: issued, plate number recorded against the VIN, date received, current physical location, who is carrying them to which site, and confirmation that they reached the delivery point before the customer did. Temporary permits have validity dates that need watching while the vehicle is already in the customer's hands.
The failure here is mundane and common: plates for the right VIN, in the right building, on the wrong site. A delivery board that shows a green registration status while the plates are in a different city is showing a status, not a readiness.
Insurance has to move in step
Registration and insurance are separate processes joined at one point: a vehicle must be covered from the moment it goes into service, and the policy has to carry the registration number the office actually issued.
The recurring mismatches are all timing and data problems. The policy is drafted before the plate number exists and then never updated. Cover starts on a date chosen by finance rather than by the delivery schedule. A corporate or leasing customer arranges insurance externally, so nobody at the dealership can confirm it. Or a leasing fleet policy is assumed to cover a vehicle that has not yet been added to it.
Treat insurance confirmation as a gate item with a named owner and a documented confirmation, not as an assumption made on the delivery day.
Customer handover
Registration should be planned backwards from the handover date. In most dealerships it is planned forwards from vehicle arrival, which is why the two calendars diverge.
Sales teams quote delivery dates against physical availability because that is the information they have. The correction is not to slow sales down; it is to give them a different field to quote against. A handover date should be confirmed from a readiness state, and one person should have the authority to say the state has not been reached.
That produces an uncomfortable but useful conversation once. After that, the delivery board stops lying.
The file closes at the permanent certificate, not at the plates
The registration case does not close when plates are issued. Permanent certificate collection and document reconciliation are part of the dealer process.
This is the most commonly unowned task in dealer operations, because by the time the certificate is ready the vehicle has been delivered, the customer is satisfied, and the commercial transaction is closed. The certificate then sits uncollected, or is collected and delivered to the user instead of the legal owner, which is a genuine problem in leasing transactions where the owner is the leasing company.
Track four numbers weekly:
- certificates awaiting issue
- certificates awaiting collection, by age
- certificates collected but not yet delivered to the correct party
- confirmations outstanding from customers or leasing owners
None of these affect a delivery this week. All of them surface later, usually when a leasing company audits its document holdings or a customer needs the document for something.
Document custody discipline across a network is the subject of our page on vehicle document control in Poland.
Three operating models for a dealer network
Model A, local dealer registration. Each dealership handles its own. Strong local knowledge of the nearby office, immediate control, and the customer relationship stays in one place. Weak on consistency: twenty-five dealerships produce twenty-five processes, and network-level reporting has to be assembled by hand.
Model B, centralised network registration desk. One team coordinates for multiple dealerships. Consistent templates, one status view, specialised staff who see exceptions often enough to recognise them. Requires disciplined data handover from the sales side and a courier or electronic flow that works, and it can feel remote to a branch waiting on plates.
Model C, external registration back office. An authorised partner prepares, submits, collects and reports. Scalable, useful where volumes are uneven or offices are scattered, and it converts a fixed headcount into a variable cost. It works when the partner has a mandate to reject incomplete files rather than submit them hopefully.
None is universally right, and most large networks end up with a hybrid: central desk for standard retail, local handling where a branch has a strong relationship with its office, external support for peaks, imports and exceptions. What matters is that all three report into one VIN-level status view.
Outsourcing execution does not outsource responsibility for correct customer and transaction data. A partner can prepare and file. It cannot know that the customer changed its legal entity last week.
Standard queue and exception queue
Two queues, assigned at pack review rather than discovered at submission.
The standard queue is a new EU-approved vehicle with a correct CoC, an ordinary Polish invoice, a clear owner, complete customer documents, a standard tax position and a predictable route. In a typical importer network this is the large majority of deliveries.
The exception queue is everything else: leasing structures where documents are outstanding, foreign companies, a mismatch between the customer entity on the order and on the invoice, missing or defective authorisation, invoice corrections, missing tax documentation, imported and non-EU units, vehicles without a CoC, technical inspection cases, unusual categories, demonstrators and management vehicles, converted or multi-stage vehicles, and late VIN reassignment.
One exception should not stop the clean delivery queue. These are internal workflow categories with no legal standing, and their only purpose is throughput.
Two rules make the split work. An incomplete pack may not enter the submission queue, which means somebody needs the authority to say no. And every exception gets a category and a named owner, so a tax problem goes to the person who handles tax and an authorisation problem goes to the company secretariat. Vehicles that will not register at all are covered on our page on what to check when a vehicle cannot be registered in Poland, and imported units without European approval are covered under registration without an EU CoC.
Fleet sales: one customer, forty files
A dealer sells 40 vehicles to one corporate customer. One relationship, one contract, one delivery project, one invoice run.
And still 40 VINs, 40 registration cases, 40 plate and document statuses, and 40 lines in the tax evidence log. There is no collective registration application for a fleet.
What can be centralised is everything around the files: one set of corporate documents, one authorisation structure, one data template validated once against the customer's register entry, batched submission, one status report to the customer's fleet manager, and one collection run for plates. What stays per vehicle is the file itself and its outcome.
The practical risk in fleet deliveries is concentration: one wrong field in the customer data template does not produce one rejected file, it produces forty. Validate the template on the first vehicle before processing the rest.
Leasing deliveries
In a leasing transaction the leasing company is normally the legal owner and the registration applicant, the end customer is the user, and the dealer supplies the vehicle. Registration may be handled by the lessor, by the dealer under authorisation, or by an external partner engaged by either.
Three things should be confirmed before a handover date is given to the end customer: which entity is the owner and exactly how its name and data appear in its register entry, who will file and under whose authorisation, and where the permanent certificate is to be delivered. The third is the one that produces disputes months later.
Demonstrators, management and press vehicles
These follow their own logic and should not sit in the customer delivery queue. Ownership is usually the dealership or the importer, the use case is internal, and the timing is driven by launch or demonstration schedules rather than by a customer waiting in reception. The related readiness work around model launches is covered on our page on automotive launch readiness in Poland.
Imported and non-standard stock in a dealer network
Most dealer registrations are domestic stock. The ones that break the rhythm are units that arrived another way: a vehicle brought in from another EU market to fill a specification gap, a non-EU unit, a vehicle bought from another group company.
Two points matter operationally. These need a different pack, including the foreign registration document, the ownership chain, translations where the documents fall outside the harmonised registration data, and tax documentation appropriate to the route. And where a vehicle brought in from another EU state is sold before the registration deadline expires, the seller ceases to be the owner and the obligation passes to the buyer, which is directly relevant to how trade stock is handled.
The upstream side of getting vehicles into the network in the first place is covered on our page on finished vehicle logistics in Poland.
Where delays actually come from
Calling everything a registration delay prevents the fix. Four owners, four different corrections.
Dealer-controlled: wrong customer data, late invoice, late or defective authorisation, VIN reassigned after the pack was prepared, delayed system updates.
Importer or supplier-controlled: missing CoC, incorrect vehicle data, tax documentation not passed down with the vehicle.
Registration partner-controlled: file preparation, submission, status monitoring, plate and certificate collection.
Authority-controlled: processing, decision, document production.
In most networks the first category dominates, and it is the one nobody measures because it sits inside the commercial process rather than in the registration one.
How to measure a dealer registration operation
- registration packs received against packs complete at first review
- first-time-right submission rate
- elapsed time from complete pack to submission
- submissions per day and per week, by dealership
- open exceptions, by category, and average exception age
- vehicles physically ready but registration-blocked
- vehicles registered but not handover-ready
- permanent certificates outstanding, by age
- customer delivery dates missed because of registration, by delay category
- rework rate per dealership
- document-return backlog
Two change behaviour fastest. Packs complete at first review tells you whether the sales-to-registration handover works, and it is a dealership-level number that makes differences visible across a network. Average exception age tells you whether anyone is actually working the queue rather than reporting it.
When external registration support is worth it
A dealership with steady volume, one nearby office and an experienced administrator does not need help, and should not buy it.
Support earns its place at network scale: multiple dealerships filing in multiple offices, monthly volumes where a repeated data error becomes a serious number, a meaningful share of leasing and fleet transactions, imported or non-EU units in the mix, seasonal peaks that would otherwise need permanent headcount, or a delivery promise that depends on administrative turnaround the branch cannot flex.
AkcyzaWarszawa.pl handles vehicle registration in Warsaw and the surrounding area, with excise and vehicle documentation support across Poland, including dealer and importer operations, fleets, leasing structures, imported and non-EU vehicles and cases requiring approval procedures. For a network, the useful starting point is a workflow review on one month of real deliveries, including the ones that went wrong. The broader scope is on our vehicle registration and import services for companies page.
3. DEALER REGISTRATION LIFECYCLE
ORDER / SALE CONFIRMED → VIN ASSIGNED → REGISTRATION PACK COMPLETE → CUSTOMER / OWNER VERIFIED → AUTHORISATION READY → REGISTRATION SUBMITTED → PLATES AND TEMPORARY PERMIT RECEIVED → INSURANCE CONFIRMED → VEHICLE RELEASED FOR HANDOVER → PERMANENT CERTIFICATE COLLECTED → FILE CLOSED
| Stage | What it produces | Control point | Owner |
|---|---|---|---|
| Order / sale confirmed | Transaction type known: retail, corporate, leasing, fleet | Owner, buyer and user identified as separate fields | Sales |
| VIN assigned | Vehicle record opened | VIN becomes the primary key; reassignment is a change event | Sales operations |
| Registration pack complete | Documents assembled per VIN | Standard or exception pack decided here | Registration desk |
| Customer / owner verified | Legal data validated against registers | Verification at order confirmation, not at submission | Sales with back office |
| Authorisation ready | Signed, correct signatory, covers filing and collection | Signatory checked against the register | Back office |
| Registration submitted | Case filed at the competent authority | Authority determined from owner data | Registration desk or partner |
| Plates and temporary permit received | Physical assets in hand | Plate number matched to VIN, location recorded | Registration desk |
| Insurance confirmed | Cover in force with the correct registration number | Documented confirmation, not assumption | Sales or customer |
| Vehicle released for handover | Handover gate passed | Named release authority | Delivery manager |
| Permanent certificate collected | Final document obtained | Routed to the legal owner, not the user | Registration desk |
| File closed | Documents reconciled, systems updated | Exception closed, archive updated | Back office |
Registration is not finished when the plates arrive.
4. REGISTRATION-TO-HANDOVER GATE
An internal dealer-control framework, not a Polish statutory form. All items true before the vehicle is released to the customer.
| # | Gate item | Evidence | Owner |
|---|---|---|---|
| 1 | Correct VIN on every document | Pack cross-check against the vehicle | Registration desk |
| 2 | Correct legal owner | Register entry or personal document | Back office |
| 3 | Correct registration applicant identified | Consistent with the invoice and authorisation | Back office |
| 4 | Registration completed | Decision issued | Registration desk or partner |
| 5 | Plates physically available at the delivery site | Location confirmation, plate number matched to VIN | Registration desk |
| 6 | Temporary permit available and matched | Document in hand, validity date recorded | Registration desk |
| 7 | Insurance confirmed from the handover date | Policy confirmation carrying the registration number | Sales or customer |
| 8 | Customer or lessee paperwork complete | Contract, delivery documents, lessor confirmation | Sales |
| 9 | Dealer system updated | Registration number recorded against the VIN | Sales operations |
| 10 | Delivery authorisation released | Named person signs off | Delivery manager |
If any item is open, the handover date is a forecast, not a commitment.
5. REGISTRATION PACK COMPLETENESS CHECK
Run per VIN before the vehicle enters the submission queue.
| # | Question | Acceptable answer | If unresolved |
|---|---|---|---|
| 1 | Who is the owner? | Named entity or person, as it appears in the register or identity document | Ownership exception |
| 2 | Who is the registration applicant? | Identified and consistent with the invoice | Ownership exception |
| 3 | Is the ownership document correct? | Invoice or other document naming the correct party | Document exception |
| 4 | Does the CoC match the VIN? | Character-by-character | Technical exception |
| 5 | Is the tax position closed? | Payment confirmation, no-excise document or exemption certificate held | Tax exception |
| 6 | Is the authorisation valid? | Signed by a currently authorised representative, covering filing and collection | Authorisation exception |
| 7 | Is the correct authority identified? | Determined from the owner's residence or seat | Jurisdiction exception |
| 8 | Is any technical or import document missing? | None outstanding, or listed with an owner and a date | Technical or document exception |
If one question is unresolved, the vehicle does not enter the submission queue.
6. OWNER / CUSTOMER / USER / APPLICANT MODEL
| Role | Definition | Retail sale | Corporate sale | Leasing | Rental / mobility | Foreign buyer |
|---|---|---|---|---|---|---|
| Legal owner | Holds title | The buyer | The company | Leasing company | Fleet or financing entity | Foreign entity or its Polish company |
| Buyer / customer | Commercial counterparty | The buyer | The company | The leasing company buys; the customer contracts with it | Fleet operator | Foreign entity |
| User | Drives the vehicle | The buyer | An employee | The lessee | Rental customers | Employee or operator |
| Registration applicant | Named in the application | The owner | The company | Usually the lessor | Owner or entrusted Polish entity | Polish entity, or an entrusted holder |
| Registration operator | Prepares and files under authorisation | Dealer representative | Dealer or partner | Lessor, dealer or partner | Partner | Partner |
The dealer is almost always the operator and almost never the owner. Systems that call the buyer "the customer" and stop there produce applications filed with the wrong party's data.
7. CENTRALISED DEALER REGISTRATION MODEL
DEALER SALES TEAM → CENTRAL REGISTRATION DESK → REGISTRATION AUTHORITY → CENTRAL STATUS CONTROL → DEALER → CUSTOMER HANDOVER
| Step | What moves | What must be true |
|---|---|---|
| Dealer sales team | Customer and transaction data, VIN, invoice, signed authorisation | Data validated at order confirmation; one template across the network |
| Central registration desk | Complete pack, submission decision | Mandate to reject incomplete packs; standard and exception queues separated |
| Registration authority | The application, per VIN | Authority determined from the owner's data, not the dealership's location |
| Central status control | VIN-level status back to the branch | One status view across all dealerships and all channels |
| Dealer | Plates, temporary permit, readiness signal | Plates physically at the delivery site before the handover slot is confirmed |
| Customer handover | Vehicle released | Handover gate passed |
A dealer network can centralise registration operations without treating individual VINs as one legal case. The branch keeps the customer relationship; the desk keeps the process.
8. DEALER REGISTRATION CONTROL MATRIX
An internal dealer operations tool, not an official government form.
| Field | What it records | Why it earns its column |
|---|---|---|
| VIN | Primary key | The only identifier present from allocation to certificate |
| Dealer / branch | Delivering location | Network-level performance and plate logistics |
| Customer | Commercial counterparty | Not the same field as owner |
| Legal owner | Title holder | Determines the competent authority and the applicant |
| User / lessee | Who drives it | Documents must not be routed here by default |
| Invoice status | Issued, corrected, matching the owner | Invoice-owner mismatch is a top-three blocker |
| CoC status | Held, matched to VIN | Checked, not assumed |
| Tax status | Payment confirmation, no-excise document, exemption certificate, outstanding | Blocks the file if missing |
| Authorisation status | Template version, signatory, scope, filed | Must cover collection as well as filing |
| Technical inspection | Required, exempt, done | Relevant mainly to imported units |
| Registration authority | Which office | Determined from owner data |
| Submission status and date | Not ready, submitted, decided | Start of authority-controlled time |
| Plates | Issued, number, matched to VIN, current location | Physical asset, not a status |
| Temporary permit | Issued, validity date | Expiry while the customer has the car |
| Insurance active | From date, registration number matched | Gate item |
| Customer delivery date | Promised date | The commitment everything is measured against |
| Handover-ready? | Yes / no | The field sales should quote against |
| Permanent certificate | Awaiting issue, awaiting collection, collected | The unowned task |
| Certificate delivered to | Legal owner, with confirmation | Leasing disputes start here |
| Original documents reconciled | Yes / no | File closure condition |
| Exception type | One of the nine categories | Routes the problem |
| Responsible person | Name and function | A blocker without an owner is a status |
| Next action and due date | Concrete step | Tied to the delivery date |
9. STANDARD QUEUE VS EXCEPTION QUEUE
| Standard queue | Exception queue | |
|---|---|---|
| Vehicle | New, EU-approved, Polish stock | Imported, non-EU, no CoC, converted or multi-stage, unusual category, demonstrator or management vehicle |
| Buyer | Private or Polish corporate, data verified | Foreign company, entity changed after order, customer data unverifiable |
| Ownership | Buyer is the owner | Leasing structure, entrusted vehicle, financing party involved |
| Documents | Invoice correct, CoC matched, customer documents complete | Invoice correction needed, CoC mismatch, missing originals |
| Authorisation | Standard template, valid signatory | Missing, wrong signatory, scope too narrow |
| Tax | Position closed and evidenced | Document outstanding or route unclear |
| Allocation | VIN stable | Late reassignment by sales |
| Handling | Batched submission, standard lead time | Named owner, exception category, separate reporting, delivery date re-forecast |
| Goal | Throughput and on-time handover | Resolution without blocking the clean queue |
Internal workflow categories with no legal standing.
10. DEALER EXCEPTION TAXONOMY
Every exception record carries: VIN · type · responsible party · blocker · next action · customer delivery impact.
| # | Category | Typical trigger | Resolved by | Delivery impact |
|---|---|---|---|---|
| 1 | Customer data | Wrong legal name, address, register details, identity data | Sales, with the customer | Usually days |
| 2 | Ownership | Invoice names a different party from the intended owner; leasing details late | Sales with the lessor | Days to weeks |
| 3 | Authorisation | Missing, wrong signatory, scope excludes collection | Back office and the customer's secretariat | Days |
| 4 | Tax | Payment confirmation, no-excise document or exemption certificate outstanding | Back office with the importer or tax office | Days |
| 5 | Document | Missing original, invoice correction, translation needed | Dealer and supplier | Days to weeks |
| 6 | Technical | CoC mismatch, inspection required, data discrepancy | Importer, inspection station | Weeks |
| 7 | Approval | No CoC, non-EU specification, multi-stage vehicle | Approval specialist | Weeks or longer |
| 8 | Authority / jurisdiction | Wrong office identified, owner in another district, entrusted structure | Back office | Days |
| 9 | Insurance / handover | Cover not confirmed, registration number mismatch, release not authorised | Sales and customer | Same day, if caught |
11. DEALER FILE CLOSURE CHECK
A registration case is closed only when all of the following are true:
| # | Condition | Evidence |
|---|---|---|
| 1 | Registration status confirmed | Decision recorded against the VIN |
| 2 | Plates reconciled | Plate number matched to VIN, delivery confirmed |
| 3 | Temporary permit tracked to expiry or superseded | Date recorded |
| 4 | Permanent certificate collected | Collection confirmation |
| 5 | Certificate routed to the correct party | Delivered to the legal owner, with confirmation |
| 6 | Original documents reconciled | Custody record complete |
| 7 | Dealer system updated | Registration number and status against the VIN |
| 8 | Exception closed | No open items on the record |
A vehicle delivered to a happy customer is not a closed file.
12. DELAY ATTRIBUTION MODEL
| Category | Typical causes | Can it be committed to in an SLA? | The fix |
|---|---|---|---|
| Dealer-controlled | Wrong customer data, late invoice, late or defective authorisation, VIN reassigned after pack preparation, system updates | Yes, internally | Validate data at order confirmation; one authorisation template |
| Importer / supplier-controlled | Missing CoC, incorrect vehicle data, tax documentation not passed down | Partly, through supply terms | Make document despatch a delivery condition |
| Registration partner-controlled | Pack review, submission, monitoring, plate and certificate collection | Yes | Measure first-time-right and time-to-submission |
| Authority-controlled | Processing, decision, document production | No | Plan buffer, report honestly |
A network review that concludes "registration was slow" has identified nothing. One that shows most lost days were customer-data corrections leads to a change in the sales process.
13. DEALER DELIVERY RISK DASHBOARD
Internal operational statuses, not legal categories.
| Status | Meaning | Typical contents | Action |
|---|---|---|---|
| GREEN | Registration complete and handover-ready | Gate items all closed | Confirm the delivery slot |
| AMBER | Expected to be ready, one controllable action remains | Plates in transit, insurance confirmation pending, system update outstanding | Named owner, action due before the delivery date |
| RED | Customer delivery date at risk | Authorisation defective, tax document outstanding, invoice correction needed | Re-forecast the date and tell sales today |
| BLACK / HOLD | Cannot proceed until a structural issue is resolved | CoC mismatch, no approval route, customer entity changed, ownership unresolved | Remove from the delivery schedule; move to exception queue with a decision owner |
The value of the fourth status is that it stops a vehicle being re-promised weekly.
14. RESPONSIBILITY MATRIX
S = source data. E = execution. C = control and confirmation.
| Task | Dealer sales | Dealer back office | Importer | Registration partner | Customer / lessor | Authority |
|---|---|---|---|---|---|---|
| Customer and owner data | S | C | — | verification | S | — |
| Invoice / ownership document | S (issue) | C | — | check | — | requires it |
| Certificate of conformity | — | C | S | check | — | requires it |
| Tax evidence | — | C | S (pass down) | E | — | issues document |
| Authorisation | request | C | — | E (use and file) | S (sign) | verifies |
| Determining the authority | — | C | — | C | — | — |
| Submission | — | possible E | — | E | possible E | processes |
| Plates and temporary permit | receives | C | — | E (collect) | — | issues |
| Insurance | C | — | — | — | S | — |
| System update | E | C | — | status feed | — | — |
| Handover release | E | C | — | readiness signal | receives | — |
| Permanent certificate | — | C | — | E (collect, deliver) | receives | issues |
| Document reconciliation | — | E + C | — | supports | confirms | — |
Source data ownership, execution and control are three different responsibilities. Most dealer registration failures happen where one party is assumed to hold two of them.
15. COMMON DEALER REGISTRATION FAILURES
Delivery date promised before the pack is reviewed. The customer is disappointed by something unrelated to the vehicle. Check earlier: quote against a readiness state, not against arrival.
The invoice names a different party from the registration applicant. The file is returned and the invoice has to be reissued. Check earlier: owner and applicant validated at order confirmation.
Leasing company details arrive late. The pack cannot be completed and the handover slot is already booked. Check earlier: lessor data and authorisation as a precondition for scheduling delivery.
CoC does not match the VIN. Usually a reassignment or a mis-picked document. Check earlier: character-by-character match at pack review.
Wrong company address. The competent authority is wrong, or the file is returned. Check earlier: validate against the register, not against the CRM.
Authorisation signed by the wrong representative. Everything else is correct and nothing can be filed. Check earlier: maintain a signatory register for recurring corporate and leasing customers.
Tax document missing. Including the exemption certificate for an EV, which owes nothing. Check earlier: tax evidence as a mandatory field per VIN.
An imported unit handled as ordinary Polish stock. It needs a different pack and a longer lead time. Check earlier: route assigned at allocation.
Insurance not synchronised with registration. Plates issued, cover starts later. Check earlier: insurance as a gate item with a documented confirmation.
Plates received but assigned incorrectly. Right plates, wrong site or wrong VIN. Check earlier: plate number recorded against the VIN with a physical location field.
VIN reassigned by sales after the file is prepared. Every prepared document now refers to a different car. Check earlier: reassignment is a change event that reopens the pack.
Temporary permit not tracked. Expiry discovered by the customer. Check earlier: validity date as a field, monitored weekly.
Permanent certificate never collected. Surfaces months later. Check earlier: weekly ageing report with a named owner.
Documents delivered to the user instead of the legal owner. Standard in leasing transactions, and a genuine dispute. Check earlier: the delivery address for the certificate comes from the owner field, not the customer field.
An exception vehicle hidden inside the standard queue. Found at submission, after the delivery date was promised. Check earlier: pack review with authority to reroute.
The sales system says ready while the registration system says pending. Two versions of the truth. Check earlier: one status field, sourced from the registration record.
The customer company changes before delivery. A new legal entity is a new case. Check earlier: freeze customer entity data at a defined point and treat later changes as change events.
Dealer and registration partner maintain different VIN lists. Reconciliation becomes archaeology. Check earlier: one master list, one owner, shared view.
Systemic errors. A wrong importer data template, an authorisation template rejected across several offices, wrong owner logic applied to all leasing customers, a tax document assumption applied network-wide, or one CoC data issue repeated across a model batch. A registration error repeated across 100 vehicles is not a vehicle problem. It is a dealer-process problem, and it should trigger a review of the rule that produced it rather than 100 individual corrections.
16. FAQ
Can a car dealer register a vehicle for the customer in Poland? Yes. An authorised representative of the sales showroom where the vehicle was purchased may file the registration application for the buyer. It requires a written authorisation from the owner, or from a representative of the company that owns the vehicle, and the dealership needs a company e-Doręggenia mailbox, since this matter is handled electronically through e-Doręczenia. The authorisation should also cover collection of the temporary registration decision, the temporary permit and the legalised plates, not only the filing.
What documents should be in a dealer registration pack? For a standard new vehicle from Polish stock: the invoice or other ownership document, the certificate of conformity, evidence of the vehicle's tax position, the customer's or company's identification data, and the signed authorisation. Exception packs add leasing or corporate documents, foreign representation documents, the foreign registration certificate and ownership chain for imported units, customs documentation, translations, and technical or final-stage documents where relevant.
Can vehicle registration be centralised across a dealer network? Yes, and most large networks do. A central desk can hold the templates, the data standard, the submission planning, the status view and the certificate collection routine. What cannot be centralised is the legal case: each vehicle is registered individually, at the authority competent for its owner, on its own file.
Can dealer registration be outsourced? Yes, under authorisation. An external partner can review packs, prepare and submit applications, collect plates, temporary permits and permanent certificates, and report status per VIN. What stays with the dealer is responsibility for correct customer and transaction data, because no partner can know that a customer changed its legal entity last week.
How does dealer registration work for leasing vehicles? The leasing company is normally the legal owner and the registration applicant, the end customer is the user, and the dealer supplies the vehicle. Registration may be handled by the lessor, by the dealer under authorisation, or by a partner. Before a handover date is promised, confirm the owner's exact registered data, who files and under whose authorisation, and where the permanent certificate is to be delivered.
Can a customer collect a vehicle before the permanent registration certificate is issued? Yes. When the application is accepted the office issues a temporary permit and plates, and the permanent certificate follows. The vehicle can be used in the meantime, provided insurance is in force. The risk is administrative rather than legal: temporary permits expire, and permanent certificates that nobody collects become a problem months later.
Who should collect the permanent registration certificate? A named person on the dealer or partner side, with the certificate then routed to the legal owner. In leasing transactions that is the leasing company, not the driver. Track certificates awaiting collection by age, because this is the most commonly unowned task in dealer registration.
What causes dealer vehicle registration delays? In most networks, customer and owner data errors, late or defective authorisations, invoice-owner mismatches and late VIN reassignment, rather than anything happening at the office. Attributing delays to four owners (dealer, importer, registration partner, authority) makes the real bottleneck visible.
Can a dealer register 50 vehicles for one corporate customer? Operationally yes, administratively as 50 individual files. There is no collective application. The corporate documents, the authorisation structure, the data template, the submission batch and the status report can all be shared. Validate the customer data template on the first vehicle, because one wrong field produces 50 rejected files rather than one.
How does electronic dealer registration work in Poland? Through e-Doręczenia. Since 1 January 2026 that is the channel for this matter, which means the dealership needs a company e-Doręczenia mailbox with named users and a signature method in place. Notification that documents are ready for collection arrives through the same channel, so the mailbox needs a daily owner. Further changes extending fully electronic registration have been moving through the legislative process, so confirm the current position before fixing a workflow in software.
17. CTA
Organising registration across a dealer network?
For an importer or dealer group, a useful first exchange is a workflow review rather than a price list. Send:
- monthly registration volume and number of dealer locations
- vehicle categories and the share of EV and imported units
- split between retail, corporate, leasing and fleet customers
- the current registration workflow, and who does what at each step
- who currently holds original documents
- who submits applications, and through which channel
- who collects plates and temporary permits
- who collects permanent certificates, and where they are delivered
- the three exception types that consume most of your team's time
From that, the process can be mapped into a standard registration queue, a leasing and corporate queue, an imported-vehicle queue and an exception queue, with customer handover controls and permanent-document follow-up defined for each.
AkcyzaWarszawa.pl — kontakt@akcyzawarszawa.pl — +48 509 274 704 Vehicle registration in Warsaw and the surrounding area. Excise and vehicle documentation support across Poland.
Potrzebujesz więcej wiedzy?
