NegzelNegzel
Contact Us
Translucent abstract data prisms representing digital document and finance flows

06NEGZEL PRODUCT FAMILY

Negzel n-Solutions

n-Solutions start where standard SAP stops. We build ready-made products that work with SAP for legal obligations, finance and foreign trade, and for textile production, quality control and maintenance; each one can be rolled out on its own and runs on the data already in your system.

Let's discuss your projectDocument journey

From shipment to ledger

Where is your document, and which product is there?

Each product digitises one stop on the document journey with your SAP data.

  1. 01 · When goods leave

    Shipment

    The dispatch note is created from the delivery in SAP and reaches the buyer through GİB; the goods travel on a separate track.

    E-Dispatch Note

    Companies that ship goods

    Issues the dispatch note electronically from the delivery in SAP, sends it to the buyer through GİB and tracks the response.

    • The dispatch note comes from the delivery, so shipping and invoicing rest on the same data
    • The buyer's acceptance or rejection returns to SAP as a dispatch response
    • Issuing, sending and response tracking happen on one screen
    Document and goods on two tracks
    e-Dispatch note: document track and goods track

    Document

    1. SAP deliveryDispatch note is created
    2. GİBDocument is transmitted
    3. Buyer's systemDispatch response returns

    Goods

    1. Leaves the warehouseGoods are loaded
    2. On the roadVehicle and driver on the note
    3. DeliveredBuyer accepts the goods

    The document reaches the buyer through GİB; the goods travel on a separate track.

  2. 02 · When the sale happens

    Invoice

    e-Invoice if the buyer is a registered e-Invoice taxpayer, e-Archive if not; a tax ID check before invoicing decides which one is issued.

    E-Invoice

    e-Invoice taxpayers

    Creates the sales invoice from the billing document in SAP and sends it to the buyer through GİB; incoming e-Invoices from suppliers land in SAP too.

    • Before invoicing, the buyer's tax ID is checked to see whether they are a registered e-Invoice taxpayer
    • Incoming invoices land in SAP; acceptance or rejection is answered from the same screen
    • The document is created inside SAP and sent without leaving for a separate portal
    Details
    • Printing, enveloping and courier work disappears; sending and posting run in the same flow.
    • Documents stay digitally accessible for the full legal retention period.
    • Access is role based, and who opened which document is tracked.

    E-Archive

    Non-registered buyers

    Issues, sends and stores invoices for buyers who are not registered e-Invoice taxpayers and for consumers, all electronically.

    • If the buyer is not an e-Invoice taxpayer, the invoice moves to the e-Archive flow on its own
    • The invoice reaches the buyer by e-mail or text message; a paper copy is available on request
    • The e-Archive report due to GİB is produced in the system
    Details
    • A sale invoiced with an e-Archive invoice needs no separate cash register (ÖKC) sales receipt; the obligation to use a cash register remains, and the sale is recorded on it with an information slip.
    • A campaign or announcement field can be added to the invoice.
    • Past invoices are viewed, downloaded and printed from one screen.

  3. 03 · When the money arrives

    Collection

    Bank transactions come into SAP; each item is linked to the right account by tax ID, national ID or IBAN and posted.

    OBI (Bank Account Statement)

    Finance teams with many banks

    Brings account transactions from your banks into SAP through a web service, links each item to the right customer or supplier account by tax ID, national ID or IBAN, and posts it.

    • Queries run from a cockpit in SAP: a company code and a date range are enough, nobody logs in to the bank
    • Each bank's statement format is converted into one structure
    • Items without a match wait on a separate list; bank and SAP balances are compared on the same screen
    How does the matching work?
    How an incoming transaction finds the right account

    Incoming bank transactionEFT or wire transfer

    Identity checkTax IDNational IDIBAN

    • Right customer or supplier accountPosted to the defined accounts
    • No matchThe item waits on a separate list

    The statement format agreed with the bank and the service user are defined once in SAP.

    • Postings can also be created for transactions other than EFT and wire transfers, such as loan principal repayments.
    • Bank passwords do not circulate among users; access runs through SAP roles.
    • Adding a new bank does not change the user's screen or flow.

  4. 04 · When an employee spends

    Expenses

    Expense and advance requests go through an approval chain; approved requests are posted in SAP.

    Employee Expenses and Advances

    Teams managing employee spend

    Collects expense and advance requests through a web and mobile interface, routes them through a defined approval chain and creates the posting in SAP once approved.

    • Approval steps follow amount, expense type and organisation; delegation and bulk approval are supported
    • Expense account, cost centre and VAT split come from a maintenance table by expense type
    • An advance stays open per employee and is cleared by the expenses entered
    Advance cycle and how it differs from SAP Concur
    Advance cycle

    Advance

    1. 01RequestAmount and reason
    2. 02ApprovalManager
    3. 03PaymentPayment posted in SAP
    4. 04SpendingExpenses and receipts entered
    5. 05SettlementRefund or extra payment

    The cycle starts over

    An advance that is not cleared shows up as an open item per employee.

    • It is Negzel's own product and takes employee, cost centre and account data straight from SAP. SAP Concur is SAP's separate cloud product, and we consult on it as well.
    • Limits are set per person and expense type; a breach is visible as soon as it is entered.
    • Vehicle use, mileage and fuel costs are tracked in the same portal.

  5. 05 · At month-end

    Period end

    Ledgers and berat files are prepared from SAP data, open balances are confirmed with business partners and the IFRS statements build up in a separate ledger.

    E-Ledger

    Companies keeping e-Ledgers

    Produces the journal and general ledger in GİB format from the postings in SAP and prepares them for upload together with their berat files.

    • Journal, general ledger and their berat files are produced to the GİB standard
    • Berat files are signed with a financial seal or a qualified electronic certificate
    • Berat files are uploaded to GİB by the end of the third month after the month of the ledger
    Monthly flow
    One month of e-Ledger
    1. 01 · During the monthPostingsEntries are created in SAP FI as usual.
    2. 02 · Month-endLedger creationJournal and general ledger are prepared for the month.
    3. 03 · CheckConsistency and approvalChecks run, opening and closing entries fall into place.
    4. 04 · SignatureBerat and signatureBerat files are produced and signed.
    5. 05 · DeadlineUpload to GİBBy the end of the third month after.

    Ledgers and berat files for the last month of the fiscal year are due by the end of the month in which the income or corporate tax return is filed.

    • Printing and certifying paper ledgers is no longer needed.
    • Opening and closing entries use their own document types and are written at the start and end of the ledger.

    E-Reconciliation

    Finance teams with many accounts

    Takes account reconciliation away from phone, post and fax: balances come from SAP, letters go out from a web application and replies are tracked on one screen.

    • Reconciliation letters go out one by one or in bulk, with preview and notes
    • Business partners who do not reply get an automatic reminder e-mail
    • Statement comparison finds the differences; agreed and rejected reconciliations are reported
    Reconciliation flow
    The path of one account reconciliation
    1. 01BalanceTaken from SAP
    2. 02LetterOne by one or in bulk
    3. 03ReplyAgreed or not
    4. 04ReminderE-mail if no reply
    5. 05DifferenceStatements compared
    • Works with SAP, connects to non-SAP systems as well and supports several company codes.
    • There is no limit on the number of users.
    • Forms Ba and Bs were abolished from the September 2024 period by Tax Procedure Law General Communiqué No. 565; reconciliation now runs on open account balances.

    IFRS Package

    Companies reporting under IFRS

    Runs a parallel IFRS ledger in SAP next to the statutory ledger and calculates period-end adjustments, from rediscounting to deferred tax, with fourteen programs.

    • Adjustments are posted to the IFRS ledger only; the statutory ledger stays as it is
    • Each program's output is available as a check report before posting
    • Runs on SAP ECC and SAP S/4HANA
    One entry, two ledgers
    One document, two valuations

    Business documentSAP FI

    Parallel ledgerTax lawTFRS

    • Statutory ledgerTax Procedure Law and the uniform chart of accounts; the package does not touch it
    • IFRS ledgerTFRS valuation and the adjustments of the fourteen programs

    Both statements come from the same data; the difference between them stays traceable every period.

    • Rates, maturities and account assignments are maintained in each program's own table.
    • Loans and investment incentive certificates are loaded from Excel.

  6. 06 · Cross-border

    Foreign trade

    Loading, customs clearance, cost allocation and the export completion date are tracked in one flow inside SAP.

    Import and Export Package

    Importers and exporters

    From purchase order to file closing on the import side, and from delivery to the export completion date on the export side, logistics, customs and accounting steps run inside SAP as one connected flow.

    • Loading, clearance, cost and invoice steps are managed from a single menu and cockpit screen
    • Customs and other import costs are allocated to purchase order items automatically
    • Export invoices post on the export completion date; proof of delivery runs in the background

From sample to maintenance

Which product works where in production and in the field?

Each product ties one moment of production or field work to SAP; the record is created where the work is done.

  1. 01 · Before the order arrives

    Sampling

    Proto, fit and pre-production sample rounds are tracked in SAP from the customer's request to approval; the approved style moves into bulk production without re-entering master data.

    Textile Sampling Cockpit

    Apparel and textile manufacturers

    Manages the sample request, bill of materials, sample room production, free-of-charge shipment and customer approval in SAP under one sample number.

    • Request, order, delivery and cost sit under the same sample number, and the round each sample is in stays visible
    • Fabric, trims, labour and subcontracting costs collect on the sample order; estimated and actual cost are compared per round
    • The approved sample's bill of materials and routing are copied to the bulk material, with no master data re-entered
    Sample flow
    The path of one sample round in SAP
    1. 01 · RequestSample cardCustomer, season, style and due date are entered; a free-of-charge sample order is created.
    2. 02 · DefinitionBill of materials and routingFabric, trims and sample room operations are defined; the cost estimate runs.
    3. 03 · ProductionSample room orderMaterial is drawn from the sample store; cutting and sewing are confirmed.
    4. 04 · ShipmentMeasurement check and dispatchMeasurements go into the inspection lot; the sample leaves with a free-of-charge delivery.
    5. 05 · ApprovalHandover to bulkIf a revision is requested, a new round opens.

    Every change to the bill of materials is recorded with a change number, and each round is kept as a separate version.

    • Built on standard objects in SAP SD, SAP PP, SAP MM, SAP QM and SAP CO; sample-specific document types, a sample card and a tracking screen are added.
    • If the tech pack and measurement chart are kept in a PLM system, they can be passed to the sample card through an interface.
    • Sample costs the company carries are reported as an expense by customer, season and sample type.

  2. 02 · As the order goes into production

    Planning

    Style, colour and size demand is placed on machine and line load; work the in-house capacity cannot take moves to a subcontractor, and the approved plan is written to standard SAP documents.

    Textile Planning Cockpit - Variant Configuration

    Textile makers planning lines and machines

    Places orders on visual planning screens by machine and sewing line load; the in-house or subcontract decision is made on the same screen, and the approved plan is written to standard SAP documents.

    • Style, colour and size breakdown is carried with SAP VC (Variant Configuration), and the plan is built on these variants
    • Machine and line load show on a Gantt chart and a load graph; overloaded lines and days are flagged in colour, and orders move by drag and drop
    • When capacity runs short, the operation moves to a subcontractor; the purchase requisition and subcontract order follow the standard SAP MM flow
    Planning flow and standard SAP
    From demand to an approved plan
    1. 01 · DemandOrders are createdThe sales order becomes a planned order through MRP, then a production order.
    2. 02 · LoadLoad is calculatedStandard minutes (SMV) in the routing and the quantity give the daily load per line and machine.
    3. 03 · PlanPlaced on the boardOrders spread across lines on a Gantt chart; utilisation and bottlenecks show.
    4. 04 · AllocationIn-house or subcontractSubcontractor capacity and price are compared on the same screen.
    5. 05 · ReleasePlan written to SAPDates and work centres go to the production order, subcontract work to a purchasing document.

    Standard SAP tables and programs are not modified; the Negzel layer reads standard data and writes the approved plan through standard interfaces.

    • Line efficiency, operator count, subcontractor capacity and plan versions are data standard SAP does not hold, so they live in the Negzel layer; plan versions are tried out without touching SAP orders.
    • Installed as an SAP Fiori app on SAP S/4HANA and as ABAP screens on SAP ECC.
    • It does not replace SAP PP/DS; where SAP PP/DS is in use, the subcontract allocation and line load screens complement it.

  3. 03 · When the product is inspected

    Quality control

    The inspector enters results on a mobile device on site; the AQL calculation and the usage decision are posted to the inspection lot in SAP QM.

    Mobile Quality Control Field App

    Quality teams and field inspectors

    Simplifies the SAP QM inspection lot, results recording and usage decision screens with SAP Fiori and takes them to phones and tablets; results the inspector enters on site are saved straight to SAP.

    • Inspection characteristics come from the material type; defects are classed as major, minor or critical
    • The AQL calculation runs on its own from the inspected quantity and the defect rate
    • Measurement tolerances come from PLM or SAP; values are entered per size and measuring point, with a photo at each step
    Inspection flow
    From assignment to usage decision
    1. 01 · PlanningAssignmentInspector workload shows on the planning screen.
    2. 02 · SelectionInspection lotThe inspector picks an assigned job; characteristics come from the material type.
    3. 03 · ResultsDefects and measurementsDefect class, measurements by size and photos.
    4. 04 · CalculationAQL evaluationThe sampling result is calculated on its own.
    5. 05 · DecisionUsage decisionResults, notes and photos go to the supplier and internal teams by e-mail.
    • Results are recorded as a summary or one by one; inspection point results and partial stock postings run from the same screens.
    • Data does not leave for a third-party system; authorisations and checks follow the definitions in SAP.
    • In-line and final inspections at subcontractors are tracked to one standard, from one place, across plants and suppliers.

  4. 04 · When a machine needs maintenance

    Maintenance

    The technician opens the work order on a device, enters the parts used and the time spent at the machine, and closes the work order in SAP PM from the field.

    Advanced Maintenance and Repair App

    Maintenance teams and field technicians

    Takes SAP PM work orders to the technician's phone or tablet: the equipment is verified by QR code, parts and time are entered on the spot, and the work order is closed in the field.

    • The technician sees the equipment's past breakdowns next to the machine; repeat failures show in the records
    • Spare parts used are posted to the work order straight away; before and after photos are attached to it
    • Records entered where there is no signal stay on the device and go to SAP once the connection returns
    Field flow
    The path of one work order in the field
    1. 01 · PlanningWork order is openedA planned or breakdown work order is created in SAP PM and assigned to a technician.
    2. 02 · On siteEquipment is verifiedScanning the QR code or barcode opens the right equipment.
    3. 03 · During the jobEntry is madeWork done, time, material and damage code are entered on the spot.
    4. 04 · EvidencePhotos are addedBefore and after shots are linked to the work order.
    5. 05 · TransferWritten to SAPRecords entered offline are sent once a connection is available.
    • Screens come with SAP Fiori and open the same way on phones and tablets.
    • Damage and cause codes are picked from a list, so fewer inconsistencies come from free text.
    • The maintenance planner follows job status in SAP; mean time to repair (MTTR) is measured per piece of equipment.

Let's work out which product fits you

We look at your current SAP system with you and work out which product helps at which stop.

Request a meeting

OUTCOMES FIRST

Business outcomes

  1. 01

    End-to-end visibility

    The same transaction chain can be followed from the SAP document to its status on the external platform.

  2. 02

    Less manual work

    Controlled automation in the document, bank transaction, error and reprocessing steps.

  3. 03

    Operations ready for regulation

    Managing changes through product, integration, testing and support routines.

OVERVIEW

Scope and approach

When digital document processes stay as separate applications that only answer regulation, manual checks, reconciliation and errors pile up. Negzel n-Solutions places these flows inside finance and operations processes.

The e-document and finance products handle legal obligations, collections, employee spend and period end from inside SAP; the Import and Export Package tracks the foreign trade file on the same SAP data. The production and field products tie textile samples, capacity plans, quality inspections and maintenance work orders to SAP where the work is done.

Creating, sending, tracking and archiving e-Invoice, e-Archive and e-Dispatch documents is tied to SAP business documents. Users see what happened and what to do in business terms instead of technical messages, and monitoring and support work the same way across the family.

FOCUS

What do we solve?

  1. Scattered document tracking

    We link the document life cycle to the SAP transaction ID and build a single view.

  2. Errors noticed too late

    We make the status, the cause of the error, the owner and the reprocessing action visible.

  3. Manual bank reconciliation

    In the OBİ flow we classify transactions by rules and put them in front of the finance team for review.

E-DOCUMENT INTEGRATION

Special integrator or direct GİB integration?

For e-Invoice, e-Archive, e-Dispatch and e-Ledger we set up the SAP side; how the document travels to GİB, the Turkish Revenue Administration, is your decision. Negzel is not a special integrator: if you send documents through one, we can work with almost all of GİB's authorised special integrators, and if you connect directly from your own system, we set it up with you.

In the special integrator model the taxpayer applies to the integrator of its choice, and the integrator reports the taxpayer's details to GİB. Direct integration is open to taxpayers that meet GİB's conditions: the taxpayer applies to GİB with documents describing its system and goes through a test phase. Sending documents through an integrator does not lift the taxpayer's duty to keep and present them; the difference lies in where infrastructure, signing and regulatory follow-up are handled.

Which model fits you?

The choice comes down to who carries the infrastructure, the financial seal and regulatory follow-up.

  • Through a special integrator

    Infrastructure and regulation follow-up at the integrator

    • You do not want to carry server, database and IT costs in house
    • You do not want to assign people to follow technical guide changes
    • You want to use the integrator's financial seal or HSM device instead of your own
    • You want storage, backup and an availability commitment as a service

  • Direct GİB integration

    The process stays in your own system

    • You already run servers and IT operations in house
    • You want electronic records to stay inside the company
    • You have a team to follow and apply guide updates
    • You have your own financial seal or HSM device, or plan that investment

IFRS PACKAGE

Fourteen programs that run at period end

The IFRS Package is built on the parallel ledger structure in SAP FI: the same document reaches the statutory ledger under Turkish tax law rules and the IFRS ledger with TFRS values. Standard SAP provides the parallel ledger and valuation areas; the calculations Turkish practice asks for, such as rediscounting, KGK currency valuation and deferred tax, come from the package's ready programs, which post to the IFRS ledger only.

KGK, the Turkish accounting standards authority, decides who applies TFRS: as a rule public interest entities must, while other companies subject to independent audit apply BOBİ FRS. The package is for companies that prepare IFRS statements, report to a parent abroad or apply TFRS by choice; it runs on SAP ECC and SAP S/4HANA.

The package's programs

Each program reads its own maintenance table and gives a check report before posting.

ProgramWhat it does
Discounting to present valueFinds the present value of receivables and payables not yet due on the valuation date.
Doubtful receivablesIdentifies overdue balances per account with defined maturities and rates and posts the allowance.
TFRS 9Reports financial assets and liabilities under TFRS 9 principles.
RediscountingCalculates the present value of notes and receivables not yet due and creates the adjustment entry.
ReclassificationsReclassifies expense transfers and customer and supplier balances on the wrong side by month, with a reversal the next day.
Loan provisionsCalculates interest and the internal rate of return on loans and splits short and long term from the dates.
Inventory impairmentAges stock by quantity and value and applies rates to slow-moving stock by product or material group.
Investment propertyClassifies property held for rent or appreciation separately and depreciates it on a straight-line basis.
Investment incentive certificateLoads certificate items from Excel and posts to the defined accounts when needed.
IFRS 16 leasesBrings leases onto the lessee's balance sheet under a single model; short-term leases of 12 months or less and low-value assets can be exempted.
Accruals and deferralsReclassifies expenses for the coming months to expenses for the coming years in the IFRS ledger.
Fixed assetsUpdates the IFRS ledger with IFRS values through a separate depreciation area and depreciation key.
KGK currency valuationValues accounts starting with 1 and 2 at the buying rate and those starting with 3 and 4 at the selling rate, using Central Bank rates.
Deferred taxCalculates deferred tax on temporary differences between the TFRS and tax balance sheets with the liability method and enacted rates.

The package is modular: you start with the programs that matter most for your audit and widen the scope later.

METHOD

How we work

  1. 01

    Map the process

    We map the steps where a document, bank transaction or field job starts and completes in SAP.

  2. 02

    Connect

    We design external services, data contracts, security and error patterns.

  3. 03

    Verify

    We test positive, negative, cancellation, repeat and reconciliation scenarios end to end.

  4. 04

    Run

    We put regulatory updates, monitoring, support and improvement into a sustainable model.

COMMON QUESTIONS

Frequently asked questions

Do n-Solutions work with our current SAP system?

It depends on the product. The Import and Export Package runs on SAP_BASIS 7.40 and higher: SAP S/4HANA on-premise, SAP S/4HANA Cloud Private Edition (new name: SAP Cloud ERP Private) and RISE with SAP. The IFRS Package runs on SAP ECC and SAP S/4HANA. The Textile Planning Cockpit is installed as an SAP Fiori app on SAP S/4HANA and as ABAP screens on SAP ECC, and the mobile quality control and maintenance apps come with SAP Fiori screens. For the e-document products we design the setup around your SAP release, your document processes and the connection model you choose.

What does OBİ automate?

Bringing bank transactions into SAP, matching them to the right account and posting them. The statement format agreed with the bank and the service user are defined once in SAP; after that you enter a company code and a date range in the cockpit and the query goes to the bank. Each incoming item is linked to a customer or supplier account by tax ID, national ID or IBAN and posted to the defined accounts; items without a match stay on a separate list, and bank and SAP balances are compared on the same screen.

What needs to be ready before an e-document project starts?

Six steps sit with the taxpayer and drive the timeline: the financial seal (issued by TÜBİTAK Kamu SM), the e-Invoice application to GİB (ebelge.gib.gov.tr/efaturabasvuru.html), a test server, an external (public) IP address, an SSL certificate for service traffic and a database on the server. The seal and the application depend on outside processes, so we suggest starting the project with those two.

How are regulatory changes handled?

Impact analysis, product and integration updates, regression testing, release notes and post-go-live monitoring run in one change process.

THE COMPLETE JOURNEY

Other areas of expertise

Quick access

SAP module consulting

We provide consulting across SAP modules, from finance to manufacturing and from integration to data.

Looking for the right consultant?Find an Expert SAP Consultant
Finance8
Human resources3
Logistics11
Manufacturing7
Projects and engineering2
Platform and development4
Integration2
Data and control3