Bienvenido a la facturación electrónica de Nestlé

Nestlé se ha asociado con Tungsten Network para ofrecer a los proveedores una forma más sencilla de enviar facturas

Entidades compradoras de Nestlé relevantes para la facturación electrónica con Tungsten Network

Para obtener información sobre las entidades legales de Nestlé disponibles para facturar en Tungsten Network, consulte el archivo del siguiente enlace.

Utilice esta lista para asegurarse de que ha establecido las relaciones comerciales correctas en Tungsten Network para facturar a Nestlé.

Nestlé Global - TeN Action Log (BAU)
Nestlé GlobalEI, PO, ISS21.10.2025Sofiia Rotar
Yaryna Martyniuk
Iuliia Havrut
Rayén Peláez		Iuliia Havrut
Sofiia Rotar
Yaryna Martyniuk
Pinaki Bakhat
Souren Chatterjee
Rayén Peláez
Client NameServicesCall dateAttendees
#CategoryNestlé MarketAction itemRaised byDate raisedPriorityStatusCurrent action ownerCompletion dateProgress Notes/comments
1einvoicingItaliaItaly UoM on off network invoices - 00795350Nestlé09.10.2023MediumCompleteIuliia16012024 - Rayen to forward to Mark-Julie to setup call with Professional Services
09012024 - Market liaising with suppliers to educate on UoM. No request for global solution yet.
21112023 - waiting for feedback from Italy market on volumes
14112023 - Iuliia will discuss with market which UoM are being used and legal document is XML.
07112023 - Tungsten Feedback:
SDI allows all kinds of UOMs and they do not match our UOM database codes. Since they do not have a set list of UOMs we cannot adapt to the various UOMs they are sending and so in order to avoid failures because of invalid codes we have hardcoded the UOM Each. So we will always output Each. I'd like to refer you to my initial reply as it best explains the situation:

When we receive files OFF Network, we find that they contain various units of measurement. For example, the file of the transaction AAA000260288091 contains KG_KG NETT and KG CHILOGR and not only KG. Since SDI does not have a set list of acceptable units of measurement and as it seems they do not validate them, we cannot obtain a list and without such we cannot set up the acceptable/expected units of measurement in our system so instead we have hardcoded the unit of measurement EA - Each. This is why when we receive files, we always read the unit of measurement as Each and we therefore output it on the PDF.
2einvoicingUAEClarification request dates on UAE PDF invoicesNestlé06.11.2023HighCompleteNestlé09012024 - No feedback from Market to date
21112023 - TN compliance provided update, email forwarded for Nestlé to consider on 21112023
09112023 - TN compliance will provide update middle w/c 13th November
07112023 - From: Rayen Pelaez
Sent: Monday, November 6, 2023 3:47 PM
To: Ruud van Hilten
Cc: Salaheldin,Ahmed,EG-Cairo ; Ashok, Rajesh ; Khan, Md Imran ; Ahuja,Lokesh,AE-Dubai ; Pinchuk,Oleksandr,UA-Lviv ; Almeida,Denize,BR-Ribeirão Preto ; Havrut,Iuliia-Liliia,UA-Lviv ; Hryhonets,Hanna,UA-Lviv ; Mahmoud,Salma,EG-CAIRO ; Mark Hart
Subject: RE: [EXTERNAL] Wrong invoice date replication

Hello Ruud,

This is a follow up of the attached discussion on UAE dates on the TN PDF. We had a call today with Nestlé and require further assistance from Compliance.

• Feedback provided by TN/Kofax (reiterated on our call today):
From a compliance perspective, please find attached for reference TN-Kofax feedback, provided in August:
Dear all.
As agreed, for invoices passing through a specific invboice template, Kofax changed the 'invoice sent by Tungsten Network on' into 'Invoice Issue Date' , - which we all agreed is a better description. To avoid doubt, this is the date on which the Tungsten network creates and issues the legal invoice on behalf of the supplier as per our agreements with network suppliers. All UAE invoices now have the same name label.
Again, the Tungsten Creates the legal invoice on behalf of the supplier, and the date we create and issue the invoice is the invoice date. There has been no change in logic or content to the Tungsten service, we changed the name of the invoice date field as agreed.
I hope this helps, thank you, Ruud
Therefore please note that the Tungsten PDF is the legal invoice document (not any other document) and the date we create and issue the invoice (the date the supplier sends the invoice data to TN), “invoice issue date” on the PDF, is the invoice date.

• Nestlé would like further clarification on the dates on the PDFs and what they represent and which ones should be considered: Invoice Issue Date, Delivery Date, Tax Point, Original Invoice date. From a tax perspective, Nestlé´s understanding is that it is either “Invoice issue date” or “Delivery date”, whichever one is earlier.

o Scenario 1: Example transaction AAA000262626528. It includes all these dates:

o Scenario 2: if TN/Kofax is creating the legal document on the “Invoice Issue Date”, what is the “Original Invoice date”? When will there be a “Original Invoice date”?
o Scenario 3: transaction AAA000262723696, there is a “Tax Point date” that is different to the “Invoice Issue Date”, which is the date that needs to be considered? There is no “Delivery Date”.

Thanks, Rayén
3Campaign - Supplier onboardingBeneluxBenelux market requested TN supplier on boarding campaign to take placeNestlé26.10.2023MediumCompleteIuliiaBenelux campaign in progress. Not operational point. On hold as a reference note.
09042024 - Confirmation from Artur about DNS needed.
19032024 - progress tracked in campaign call 22/03/2024 Wave 1 approx 80 suppliers
12032024 - progress tracked in campaign call
05032024 - Market will provide details in 1 week, to split in 2 waves and organise call with Ellie to go through analysis.
20022024 - Iuliia will send data for matching
23012024 - Flore would like campaign of vendors with suppliers with 10 plus volume. Waiting for Flora to provide details of contacts/emails.
16012024 - Iuliia sent reminder to market for data (contact details)
09012024 - Iuliia sent reminder to market for data (contact details)
21112023 - No input from market yet.
14112023 - Iuliia will send reminder to Flore as no input from market yet.
07112023 - Call with market took place 26.10.2023 with TN Campaign Manager, Ellie. Follow up and next steps:
From: Elitsa Petrova
Sent: Thursday, October 26, 2023 1:07 PM
To: Rayen Pelaez ; Havrut,Iuliia-Liliia,UA-Lviv ; [email protected]
Subject: RE: Nestlé Benelux - Tungsten/Kofax vendor onboarding overview

Hi Everyone,

Thank you for your time today!

Please find attached:
 The presentation we went through (in a PDF format)
 The supplier data template – mandatory fields are colored in blue.
 The supplier communications.

As discussed, we will start with the analysis next week once we get the supplier data.

Initial next steps:
 Nestlé to provide the data.
 Tungsten to analyze and report back.

Please let me know if you have any questions/concerns.

Best Wishes,
Ellie
4einvoicingGlobal (not US, not MX)TN - incorrect tax invoices with a 0% tax rateTN27.10.2023HighCompleteTN08.11.202308112023 - TN resubmission completed. Nestlé confirmed can be closed.
07112023 - Call took place 06112023. TN support carrying out actions as per file-instructions from Nestle. With Flore to finalise data file with supplier
From: Pinchuk,Oleksandr,UA-Lviv
Sent: Monday, November 6, 2023 1:48 PM
To: Pinchuk,Oleksandr,UA-Lviv; Lubczynski,Artur,PL-Warszawa,IT Finance&Control and Legal; Mark Anil; Steven Toiron; Rayen Pelaez; Havrut,Iuliia-Liliia,UA-Lviv; Hryhonets,Hanna,UA-Lviv; Ashok, Rajesh
Cc: Almeida,Denize,BR-Ribeirão Preto; Kurman,Liubov,UA-Lviv
Subject: [EXTERNAL] TN - incorrect tax invoices with a 0% tax rate
When: 06 November 2023 16:30-17:00 (UTC+02:00) Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius.
Where: Microsoft Teams Meeting

Dear @Steven Toiron and @Mark Anil,

Hope you are doing well.

We finished analyzing the list of invoices and ready to discuss next steps from your end. Please find attached file and comment to review and next actions, column AD.
 New PDF to be linked – invoice should be re-created, but do not send them to SAP.
 No further action – can be deleted without re-creation on platform.
 Paper invoice received - can be deleted without re-creation on platform.
 To be triggered again – invoice should be created and send to SAP for next posting.


@Steven Toiron ,
Let discuss additionally deadlines for:
• Invoices which should be re-created and send to SAP (more critical)
• Invoices which should be re-created without sending to SAP and table with list with new URLs.
• @Lubczynski,Artur,PL-Warszawa,IT Finance&Control and Legal could you share requirements to fields in table with URLs, which should be shared to us.
5PO servicesGlobalPO replication - 00819280Nestlé14.11.2023MediumCompleteNestlé /Iuliia02102024 - go live with fix on Nestle side 2 weeks ago. Hypercare all ok.
10 to project in progress.
05032024 - with Commercials/Miguel/Artur
20022024 - Conversations with Miguel/Artur to change connectivity type. Iuliia looking at IS to stop sending.
29012024 - Meeting took place, Nestle IT including Sridhar.
23012024 - Iuliia to provide logs and let Rayen know. Rayen to check with TN Suppport on current understanding.
16012024 - under investigation with Iuliia, looking at missing internally.
09122024 - under investigation between middleware and Nestle. Once logs available, ticket will be logged with TN.
21112023 - Nestlé/Iuliia investigating internally as seems to be linked to flow between SAP and CPI
14112023 - Nestlé/Iuliia investigating internally as seems to be linked to flow between SAP and CPI
6Campaign - Supplier onboardingSuizaSwitzerland market campaign prepNestlé09.01.2024MediumCompleteNestléSwiss campaign in progress. Not operational point. On hold as a reference note.
09042024 - progress tracked campaign call. Requested emails from scanning hub for main suppliers high vol. Also waiting for DNS question.
12032024 - progress tracked in campaign call
05032024 - In progress. Weekly calls with Market and Ellie
20022024 - Picked up on weekly call with Market regarding Campaign
23012024 - Iuliia and Carolina meeting on Friday regarding vendor check. Also regarding two entities currently not on TN.
16012024 - Data with TN to carry out match. Once Carolina is back, we will setup call with Campaign and Market.
7Invoices - PO Convert reportPaíses BajosProvide invoice header report with PO Convert yes-noNestlé09.01.2024MediumCompleteNestlé09.01.202409012024 - report already being sent:
Nestle Global Invoice Header Report PO Converted by Buyer Date Range
The last one went to [email protected] on Friday 5th January.
8Reporting RTT and campaignGlobalCleanup and RTT reportsNestlé05.03.2024MediumCompleteNestlé09042034 - Nataliia to confirm distribution list and frequency. Rayen to send one off for the last month. No changes to fields required.
02042024 - escalated to TN Reporting team. Combined report sent on Tuesdays but data is big and with blank/dot/known vendor codes
06032024 - From: Rayen Pelaez
Sent: Wednesday, March 6, 2024 4:51 PM
To: Havrut,Iuliia-Liliia,UA-Lviv
Cc: Pinchuk,Oleksandr,UA-Lviv ; Dendiuk,Nataliia,UA-Lviv
Subject: RE: RTT report for Nestle
Hello Iuliia,
I will liaise internally to action these points and will get back to you.
Regarding point 4, we recently had a request for the US market to leave the vendor code field blank – Supplier AAA000200741 Sonoco Products Company
So I think it is important that we keep the relationships with VC blank as some markets may require it blank sometimes. Shall we just cancel “.” , “known” and “AAA..”?
05032024 - Iuliia will send email with request
9Automated emails - spamItaliaTicket 00838136Nestlé21.03.2024HighCompleteTN / Nestlé09042024 - Nestle to confirm whether still ongoing as Italy have not said
01042024 - Nestle to confirm whether still ongoing
10Italy reconciliationItaliaReconciliation Nestle - SDI - TN off network invoicesNestlé16.04.2024MediumCompleteNestlé14052024 - Rayen to confirm if email addresses sent to for offnetwork can be captured in report. It can´t.
07052024 - Nataliia and Sascha to advise once tested
02052024 - Sascha to confirm distribution list
16042024 - Dear @Rayen Pelaez,
Hope you are doing well.

We have case for investigation, its regarding reconciliation invoices which were submitted on SDI and invoices which are able on TN, to avoid missed invoices.
Main question is now find the unique info between 2 systems for next merging and reconciling.

Right now on TN for each off-network invoice reference we have some ID from SDI, as example invoice marked yellow: 1190822966-1704006378711 (AAA000265766795).

But from extracted report from SDI we have another SDI/file ID started from 11….

Next questions:

1. What is the ID which you are presenting in invoice reference
2. Could we have the SDI/file ID started from 11…. In some separate report to provide right reconciliation?
3. Do you make any corrections on data which were received from SDI (invoice reference and amount) – if no it could be our unique ID as the concatenated cell.

Of course if someone from tech team can suggest another ID which we can use to compare data, it will be fine.


Thank you in advance for your feedback

Kind regards,

Oleksandr Pinchuk
Digital Optimizer

Nestle Business Services Lviv
14 Ugorska Street, LVIV,
79034, Ukraine
11Campaign - Supplier onboardingItaliaItaly campaign for foreign suppliersNestlé16.04.2024MediumCompleteTN / NestléItaly campaign in progress. Not operational point. On hold as a reference note.
07052024 - Iuliia will check internally and talk to Sascha about 4 key vendors and whether can be given to TN
02052024 - 80% volume covered by 4 suppliers. Iuliia to provide list to Ellie.
16042024 - Iuliia to discuss internally and provide list to Ellie
12Greece supplier contact detailsGreeceGreece supplier contact details reportNestlé23.04.2024MediumCompleteTN02052024 - Request to provide contacts on last invoices
13MY/SG report bank detailsMY/SGMY/SG supplier bank details reportNestlé23.04.2024MediumCompleteTN02052024 - done
14RTT report/Supplier information section on PortalAllTo confirm if supplier information portal - active/deactivate section can be capturedNestlé23.04.2024MediumCompleteTNOn hold as a reference note. Future product updates on Customer Connect/Supplier information tabs on Portal to be communicated to Nestle
27082024: additional example provided AAA573626108. TN Product confirmed known issue under TNP-40001 and which will be resolved in September release
31072024: In addition to below Jira tickets with TN Product. Under TNP-40001 we are aiming to fix this so that system displays active whenever the relationship status is either Live/RTT on our network. If it's anything else then we will display it as inactive.
https://docusphere.atlassian.net/browse/TNP-38837
https://docusphere.atlassian.net/browse/TNP-38286
19062024 - https://docusphere.atlassian.net/browse/TNP-39072 Under review with TN Product.
11062024 - https://docusphere.atlassian.net/browse/TNP-39072
Also Portal release planned on June'27 and the description is covered under TNP-38837
15GB ReportUKRequest to add additional fields to currency report & transaction reportNestlé03.05.2024MediumCompleteTN20052024 - Nestle request to include supplier VAT reg. Number in transaction report
07052024 - Rayen to check. Provided.
16Customer connect issue GlobalIssue CC approvals not coming throughNestlé28.05.2024MediumCompleteTN11062024 - Fix in place 10062024
17Linea on SDI transactionItaliaInstructions on how to populate Fattura XMLNestlé28.05.2024MediumCompleteTN
18Training SPOC/APSudáfricaOverview TNNestlé25.06.2024MediumCompleteTN / Nestlé25.06.2024 - Call scheduled 02072024
19Onboarding overview TNBalticsOverview TNNestlé24.06.2024MediumCompleteTN / Nestlé10122024: Baltics looking into paperless KPI and will revert in 2025 if onboarding needed. Depending also on Poland Mandate dates. HU, CZ, PL, Baltics
Not operational point. On hold as a reference note.
23072024: Market to make decision
20Mandate - Belgium Peppol BélgicaTN to provide input on Mandate Nestlé23.07,2024MediumCompleteTN / Julie08042025: Market decision to go with Pagero. Nestlé to request off boarding end of summer 25
Review in August - change management
25032025: when/if supplier queries about Peppol, ask them not to use TeN. After summer no new onboarding, existing shouldn´t prolong subscriptions.
18032025 call took place with Mark H and Julie. Nestle request additional information for market on TeN benefits and what it means for suppliers. Rayen to raise with Julie and Mark H
11032025 Call was cancelled. With Julie to reschedule as a priority.
04032025 - Call with Compliance team scheduled for Monday 10th with global team and BE market.
07012025 - Iuliia reached out to Julie for update
Not operational point. On hold as a reference note.
24072024:From: Rayen Pelaez
Sent: Wednesday, July 24, 2024 10:57 AM
To: Havrut,Iuliia-Liliia,UA-Lviv
Cc: Wang,Flore Xintong,NL-AMSTELVEEN ; Dendiuk,Nataliia,UA-Lviv ; Pinchuk,Oleksandr,UA-Lviv ; Mark Hart ; Julie Coyne
Subject: RE: [EXTERNAL] Peppol for Belgium suppliers

Dear Iuliia, all,

The Belgium mandate has now been passed into law (this month) and will be in place from 1st January 2026.

It is a B2B e-invoicing mandate. Peppol, which is already used for B2G transactions, is the mandated e-invoicing framework.

Belgium is a Top 10 country for Tungsten Network and we can already confirm we will be supporting Peppol in Belgium.

Our Product and Compliance teams are currently reviewing requirements.

We will reach out to you once the analysis is complete,

Just to reiterate, we are already a Peppol certified service provider in the EU (in addition to other countries, i.e. Malaysia or Australia)

23072024; Iuliia to send to email. Rayen to check with compliance team.
21Mandate - GermanyAlemaniaTN to provide input on Mandate Nestlé30.07.2024MediumCompleteTN / Nestlé10122024: TeN Mark/Julie/TC in touch with Nestle Germany, explaining solution on TeN. Web Form will be able to attach Zugferd when creating invoice.
Not operational point. On hold as a reference note.
30072024: Weekly calls taking place with German Market.
22RTB PortalAllSlowness on RTB PortalNestlé30.07.2024MediumCompleteTN03092024: Improvements seen
31072024: Call with TN Support: RTB portal working (when special characters removed from Nestle RTB response) but slow. Jira ticket logged with TN Development to review https://docusphere.atlassian.net/browse/TNP-34684
23Microsite list of entities update (Malaysia)AllMicrosite list of entities update (Malaysia)Nestlé01.07.2024MediumCompleteTN31072024: With TN Marketing
24Ocean supplier - Italy campaign escalationItaliaSupplier contact is advising Nestle Italy that they have not agreed. Supplier is live for Nestle MXNestlé06.08.2024MediumCompleteTN Campaign13082024: See email from Ellie with details of contact
06082024: Gideon to advise who at supplier side confirmed they will use existing account to send invoices to Italy
25Test accountsAllProcess for the setup of test accounts to be documented, it currently follows the same process as new accountsNestlé20.09.2024MediumCompletePS18032025: handled within Italy project
11032025: tested macros, provided feedback. With Artur/Kristina.
18022025: testing process being defined within Italy project prep before expected go ahead from market
07012025: Call scheduled 13th January
21112024: With Julie, Mark H and Nestlé
12112024: TeN to provide answer to Marcelo and Maria emails
22102024: Iuliia provided details of countries without test accounts and replicate AAAs, with Julie to progress at TeN.
15102024: Iuliia to check internally whether Nestlé would like to request test buyer account for those markets that don´t have one.
Not operational point. On hold as a reference note.
Any new entity setup requests should include the request from Nestle for replicate test accounts, if these are required.
26Invoice status (missing)AllNestlé reviewingNestlé19.09.2024MediumIn ProgressNestlé / Pinaki / Marcelo19/08/2025: one example, it will be shared with Marcelo
12/08/2025: No invoices with wrong PO at the moment. Focus on UBL.
11/06/2025: No update. Marcelo following up internally.
04/06/2025: IT Solgar invoices on network are not getting ISS updates. Iuliia will raise with Pinaki.
27052025: 1st issue fix in production, company codes. Iuliia will be checking next week as it is too soon now. Second issue still being investigated, Iuliia liaising with Nestle IT support.
20052025: Marcelo chasing internally on 1st issue, no confirmation yet it is moved to production. Second issue still being investigated.
13052025: Marcelo confirmed update for table configuration (first reason) will be moved to production 16th May. Second issue still being investigated by Nestlé.
06052025: no update from Nestlé internal. Escalated to Marcelo.
22042025:two route causes:
Nestle company code not added to specific group - US, MX. Marcelo has approved. Iuliia logged now as enhancement RITM ticket with Nestlé. RITM05746457. Nestlé to chase internally. IT to check.
Second cause still in investigation, linked to another table in SAP, possibly linked to vendor code table. Iuliia is working with Nestlé AP support team, still being looked into. INC18761553. Nestlé continue investigation. No update.
16042025:two route causes:
Nestle company code not added to specific group - US, MX. Marcelo has approved. Iuliia logged now as enhancement RITM ticket with Nestlé. RITM05746457. Nestlé to chase internally.
Second cause still in investigation, linked to another table in SAP, possibly linked to vendor code table. Iuliia is working with Nestlé AP support team, still being looked into. INC18761553. Nestlé continue investigation
08042025:two route causes:
Nestle company code not added to specific group - US, MX. Marcelo has approved. Iuliia logged now as enhancement RITM ticket with Nestlé. RITM05746457
Second cause still in investigation, linked to another table in SAP, possibly linked to vendor code table. Iuliia is working with Nestlé AP support team, still being looked into. INC18761553
01042025:two route causes: Same update: Nestle company code not added to specific group - Iuliia shared with Marcelo for approval. No update to date.
Nestle will discuss internally 2603: US, MX Second cause still in investigation, linked to another table in SAP, possibly linked to vendor code table.
25032025:two route causes: Same update: Nestle company code not added to specific group - Iuliia to share with Marcelo for approval.
Nestle will discuss internally 2603: US, MX Second cause still in investigation, linked to another table in SAP, possibly linked to vendor code table.
18032025:two route causes: Same update: Nestle company code not added to specific group (Lakshmi to approve). US, MX Second cause still in investigation, linked to another table in SAP, possibly linked to vendor code table.
04032025: two route causes: Nestle company code not added to specific group (Lakshmi to approve). US, MX. Second cause still in investigation, linked to another table in SAP, possibly linked to vendor code table.
10122024: Nestlé will review in 2025
02102024: Nestlé reviewing why not all ISS statuses sent to TN
27Portal groupingAllChange Nestle group country to CHNestlé02.10.2024LowCompleteNestlé04102024: CHS-61688 in progress
28Malaysia mandateAllhttps://tungsten-network.my.site.com/contactCustomerSupport/s/article/Malaysia-Specifics-E-invoicing-Mandate-Timeline-FAQs-MyInvois?recordId=ka0Py0000002jttIAA&language=en_USNestlé08.10.2024LowCompleteNestlé16102024: Done
15102024: TN confirmed article can be update to include reference to classification codes and also when to tick the part of mandate box if not in current phase
08.10.2024: Nestle to share request for update to article in support hub to
29SurveyAllNestlé request to include subject in Support SurveyNestlé02.10.2024LowCompleteTN15102024: TN Support confirmed reviewing Survey email to go out within hours of ticket resolved and also to add ticket subject
30South Africa testingSudáfricaSupplier test account and buyer test company code to be updated 00920790Nestlé22.10.2024MediumCompleteNestlé/MattAccount live
28012025: Nestle South Africa market to advise go live date. Kelly/Campaign to advise if IS suppliers can be included in extension campaign.
21012025: Matt will reach out to market to confirm go live date. South Africa market to confirm list of suppliers for relationship extension, request gone to Ellie.
07012025: Testing completed by Iuliia. Go live to be confirmed by Nestlé to project team.
21112024: With Julie, Mark H and Nestlé
12112024: TeN to provide answer to Marcelo and Maria emails
29102024: rayen to provide process for setting up supplier test account and requested prioritisation of ticket with Support/mapping
31Invoice header Report enhancement / Swiss fieldsSuizaNestlé CH SPOC to provide details of fields report needed, TeN to reviewNestlé29.10.2024MediumCompleteNestle / Daniela AP deptwith Market to advise when-if assistance needed
18032025: With Swiss AP market to provide more detailed instructions for supplier comms. Iuliia to send one more reminder to Fanny.
11032025: With Swiss AP market to provide more detailed instructions for supplier comms
18022025: Iuliia to chase market on clear instructions/guidance
21012025: Market to provide feedback-analysis and wording on text for TeN support hub to be updated.
12112024: Olena to provide details of example of transaction with fields-content needed.
32South Africa IS commsSudáfricaNestlé to confirm comms to send to IS South AfricaNestlé18.02.2025MediumCompleteRayen11032025: report sent, also to Navika
04032025: comms were sent last week. Rayen to provide report for vendor visibility
18022025: Iuliia to chase Navika for sign off
33Nordic ticket GlobalProcessNestlé14.02.2025MediumCompleteNataliia / Pinaki / Sascha01042025: Nestle confirmed issue resolved and credit notes being received.
25032025: Sofiia to confirm if resolved by checking if credit notes received. Ticket 00948887 closed 2103 to reverse change requested. If needed, Nestle will request reprocess via Support ticket.
18032025: Pinaki reached out to Opentext. With Sascha to escalate.
11032025 Nataliia shared list with Pinaki, Pinaki still investigating
04032025 Credit notes in Nordics, not replicating in SAP (31 cases). Nataliia will share list and examples and Pinaki Bakhat looking into why/root cause
18012025 Global einvoicing team to review internally approach
From: Rayen Pelaez
Sent: 17 February 2025 10:20
To: Riera,Maria Magdalena,ES-Esplugues Llobregat ; Mark Timoney ; Julie Coyne ; Mark Hart
Cc: Roggero,Laura Maria,CH-Vevey ; Kumar,Lakshmi,IN-Gurgaon,Transactional Procurement ; Dan,Radu,CH-Vevey ; Lino,Fernando,PA-Panama ; Cialdella,Marcelo,ES-Esplugues Llobregat
Subject: RE: [EXTERNAL] FW: PRODUCTION ISSUE on Tungsten

Hello Maria,

Hope you had a nice weekend.

It is standard best practice on our network that Lookup updates are requested by clients via a Support Ticket. Moreover, this specific request was made by the Nestlé global einvoicing team, which is why it was actioned. We have discussed with our Support Manager and if Nestlé can operate with governance, we can help by instructing our teams to action such requests only if the Support ticket is logged by a designated Nestlé contact.

We have a weekly Operational call with the global einvoicing team on Tuesdays 12CET, I can go through this with them and extend the invite if you would like to join too?

Kind regards, Rayén
34Nestlé India IndiaReprint of transactions - company name VAT reg. NumberNestlé11.02.2025MediumCompleteMarcelo / Nestle India04032025 transactions reprinted last week
18012025 Nestle to confirm whether we can go ahead and reprint
35Testing for USNATicket 00948324Nestlé18.03.2025MediumCompleteIuliia / Support / Pinaki18032025 - 00948324. Lookup updated.
36Italy new document typeItaliaNew document type TD29Nestlé17.03.2025MediumCompleteNestlé Italy market16042025: no response from Market. Global team advised to close case.
08042025: Iuliia sent reminder, no reply from market. Iuliia to send one more reminder including Marcelo and Lakshmi
25032025: with Italy market to confirm. Iuliia to send reminder.
18032025: global team to reach out to Italy market for feedaback on whether document is expected or not and what is required from TeN
37Italy Solgar invoicesItaliaItaly Solgar off network invoices not in SAPNestlé01.04.2025MediumCompleteIuliia / Pinaki13052025: Issue fixed by Nestlé regarding invoices with PO that should be sent to SAP.
06052025:Nestlé raised ticket with BSI team (middleware) who need to add configuration from development to production. Pinaki chased internally. Iuliia to send email about testing on network IT connection from UK test supplier.
22042025: Nestlé raised ticket with BSI team (middleware) who need to add configuration from development to production. ETA COB 25th April
16042025: Nestlé checking issue with BSI team (middleware) /internal escalation
08042025: 00949927 Request to provide MDNs for 2 more transactions
01042025: Iuliia to share MDNs with Pinaki to investigate where issue lies
38Italy 00950029ItaliaItaly reprocessed transactions- trx numberNestlé03.04.2025MediumIn ProgressArtur / Pinaki11/06/2025: in current profile, no checks take place and PO number is passed to SAP. Pinaki will check with Artur how it will work with new UBL profile.
04/06/2025: Focus by global IT is on UBL for Italy
27052025: Iuliia will send reminder to Artur/Pinaki as no response
20052025: Iuliia query to Artur/Pinaki. Invoice sent with PO field with 10 digits, so payload file is sent as per logic. But PO number is not valid. Pinaki to advise what happens in such cases as invoice is not in SAP.
13052025: Italy market has not advised/replied regarding logic. Iuliia sent Nestlé document to Nestlé.
06.05.2025: Italy market to confirm the logic for the transactions, especially CC. Logic document created by Nestlé shared with market to confirm.
25.04.2025: Logic working as expected. No issue.
From: Service Cloud - Case Support [email protected]
Sent: Friday, April 25, 2025 10:24 AM
To: Havrut,Iuliia-Liliia,UA-Lviv,Accounts Payable Services
Subject: Tungsten Network - Case # 00953274: Missing invoices [ ref:!00D580H7q6.!500Py0M3p6e:ref ]

This message is from an EXTERNAL SENDER. BE CAUTIOUS, particularly with links and attachments.
________________________________________
Hello Iuliia-Liliia,

Thank you for your time on the matter.

The Payload for these transactions was suppressed and not sent to your side (not by connectivity nor email) because the Buyer VAT reg. number on the invoices is “IT00777280157” and the < SoggettoEmittente> is CC

This is in accordance with the logic provided by Nestlé for Payload 3– see attached Nestlé document Tungsten_Payload LOGIC_Update NEW (004).docx for reference:

(2.) Buyer VAT is IT00777280157 or IT00753740158 or 00777280157 or 00753740158 or 10805410965 or IT10805410965 and < SoggettoEmittente> is CC

Attached is also a screenshot of the Fattura XML for your reference.
22042025: TeN to re-check email sent for examples 00953274
16042025: TeN to check email sent for examples 00953274
08042025: with TeN support to provide trx numbers
39South Africa new Tax rateSudáfricaSouth Africa new Tax rateTeN21.04.2025MediumCompletePinaki/Nestlé ZA29.04.2025: Note that the government in South Africa has postponed the replacement of the VAT rate previously scheduled for 1 May 2025. The Standard VAT Rate will remain at 15%, and will not be increased to 15.5% until further notice.
The government of South Africa has not provided a new date for the rate change.
22.04.2025 Pinaki to check if Tax code is setup in SAP and Market ZA to confirm also available
40Tax code reportIT, UK, CH, MYTax code report - IT, UK, CH, MYNestlé06.05.2025MediumCompleteIuliia/Rayen07.05.2025: reports provided by TeN
06.05.2025: Iuliia to confirm fields, Rayen to raise with PS/reporting
41TeN Product notesAllTeN Product notesTeN04.06.2025N/ACompleteN/A02/06/2025:
From: Rayen Pelaez
Sent: 02 June 2025 16:16
To: Havrut,Iuliia-Liliia,UA-Lviv,Accounts Payable Services ; Rotar,Sofiia,UA-Lviv,Accounts Payable Services
Cc: tungsten-network.suppliers_HQ ([email protected])
Subject: Product release notes - TeN

Hello Iuliia, Sofiia,

Hope you are having a nice start to the week.

We are planning to make Product release notes available to all TeN users (Buyers, WF and IS), and therefore also Nestlé users, in your Tungsten Portal account:



They will be published in English.

For now, they are also made available on our website and I have attached a word document on how you can find them.

We will let you know when we have confirmation when they will be made available in the Portal in June.

Kind regards, Rayén
42MFA deadline 24th JuneAllMFA deadline 24th JuneTeNN/AN/ACompleteN/A11/06/2025: final deadline for all users to chose new MFA options 24th June. Comms will be sent to all users that have not made update, Portal message will also be in place.
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
43Swiss commsCHComms/portal message regarding bank details and IBANNestléN/AMediumCompleteIuliia23/07/2025: Received text from Nathalie Genoud. Portal message in place.
08/07/2025: Iuliia to follow up for final versions
01/07/2025: Nestle will provide foreign and local versions for Portal messages. TeN to setup.
44Tungsten Network certificate change noticeGlobalTungsten Network certificate change noticeNestlé21.04.2025HighCompleteNestlé12/08/2025: Opentext confirmed certificate updated.
21/07/2025:
This email notification is sent from a mailbox that isn’t monitored. Please do not reply to it.
To contact our Technical Support, please raise a case.Dear Tungsten Customers,

Tungsten Network is scheduled to change our expiring Production environment Certificate on 11th August 2025 (Monday) between 13:00 and 15:00 UTC.

It is IMPORTANT THAT YOU CHANGE THE CERTIFICATE during this change window otherwise your connections to Tungsten, post this change, will be failing.

The certificate change will affect all Customers that connect to Production environment Tungsten Network via the AS2 over HTTP, AS2 over HTTPs and SFTP/SSH connectivity.

URL: FT.TUNGSTEN-NETWORK.COM


What is the required action for Certificate change?

1. If you connect to Tungsten via AS2 over HTTP connection, you will need to change Tungsten’s AS2 Encryption & Signing (FT.TUNGSTEN-NETWORK.COM) certificate to the new certificate version.
2. If you connect to Tungsten via AS2 over HTTPs connection, then you will need to change Tungsten’s AS2 Encryption & Signing (FT.TUNGSTEN-NETWORK.COM) certificate together with the SSL certificate.
3. If you are using SFTP/SSH protocols to connect to us, you will need to change the SSH fingerprint key. The SSH fingerprint key update is system invoked. Therefore, it will trigger upon your next connection attempt, and you will only need to accept the new fingerprint.
Certificates are available below, in different formats with the respective usage:
• CA certificate: Only Certificate Authority (.cer)
• Full chain certificate Root, Intermediate & CA (.p7b)
• SSH host public key (.pub)



Certificate: SSL and AS2 (Signing and Encryption)
Download Certificate


SSH host public key
Download Key


SSH host fingerprint (SHA256)
CoimLsYqf2gphlQfp/rx/BRjEMLXyML8JF+WeIfM2S8



SSH host fingerprint (SHA1)
r0XPrQzU0SF1t+d2KSD/aSP9pOI



SSH host fingerprint (MD5)
08:02:a8:57:1d:0a:6c:d9:79:47:74:6e:01:38:29:bb



Important: failure to comply with this request will render you unable to connect to Tungsten Network and unable to transmit invoice data, so please ensure you follow these instructions.

Thank you for your cooperation,
Tungsten Automation

FAQs

1.Why is the change taking place?
Tungsten’s Production environment AS2 Encryption & Signing, SSH and SSL certificate is expiring on 13th Aug 2025 (Wednesday).

2.Tungsten's Production environment expiring AS2 Encryption & Signing, SSH and SSL certificate details:
URL: FT.TUNGSTEN-NETWORK.COM
• Serial number: 008f32145803ec6ceeb6fc5308bd2caa12
• Expiry date: 13th Aug 2025 (Wednesday)
3. When is the certificate change taking place?
11th August 2025 (Monday) between 13:00 and 15:00 UTC.

4. Can I do it another time?
No. You are required to make the change at this window because this is a Tungsten Network environment wide change that can only be made at one time.

5. Is there a way for me to test the new certificate in advance, before the given change window?
No. This is a global change in the production environment and needs to happen at the specified time given, as mentioned above.

6. There are two types of certificates formats after I’ve downloaded it (.cer and .p7b) , which type of certificate should I apply?
• If your system is expecting a full chain certificate, please install the .p7b
• If your system is expecting only the SSL certificate, please install the .cer

7. I’m seeing an error on HTTPs header level reflecting SSL connection issue via AS2, what should I do?
Most likely this is due to your system having explicit options for SSL, signing & encryption. Please ensure you apply the certificate explicitly.

8. I’m seeing errors indicating files could not be decrypted or sent via AS2 over HTTP/s connection, what should I do?
• Please ensure that you are using the correct Tungsten AS2 encryption and signing public certificate.
• Please check the serial number of the new Tungsten AS2 encryption and signing public certificate on your system and whether it matches with the new certificate you have downloaded.
• New Tungsten certificate serial number: A8990AED23EE455C5AEA1A0C165433DE
• For any issues encountered post certificate change, you may create a ticket to our support team.
9. I’m only using one encryption or signing certificate via AS2, can I still use this new certificate?
Yes, the new certificate can be applied and used for both encryption and signing.

10. I’m seeing errors indicating unable to connect to via SFTP/SSH connection, what should I do?
SSH fingerprint key update is system invoked. Please make sure that you have accepted this new SSH fingerprint key upon your next connection attempt.

11. I’m using a script or application that does not allow me to accept this manually (via SFTP/SSH connection), what should I do?
• Please download the certificate and manually install/apply it onto your script or application.
• The SSH fingerprint key is embedded together with the new Tungsten certificate.
12. Anything else required other than replacing the new Tungsten AS2, SSL and SSH certificate?
No. This certificate change only applies for connection to Tungsten via AS2 over HTTP, AS2 over HTTPs and SFTP/SSH.

Thank you for your cooperation,
Tungsten Automation
45Nestlé / supplier VAT reg. number validationItaliaNestlé supplier VAT reg. number validationNestlé23.07.2025HighIn ProgressJulieApproach changed for Italy. Nestle will not receive vendor code in UBL. Supplier VAT reg. number checked for vendor code. if multiple vendor codes found, will drop out and manual check requiredsupplier i. VMD in Italy is clean so it works. For crossborder invoices, supplier provides NA, then it will drop out. This won't work for other markets.
07/10/2025: TeN to provide update by COB w/c 6th october
12/08/2025: discussing as part of next country waves requirements
From: Havrut,Iuliia-Liliia,UA-Lviv,Accounts Payable Services
Sent: Wednesday, July 23, 2025 10:53 AM
To: Julie Coyne ; Rayen Pelaez
Cc: Hadzalo,Nadiia,UA-Lviv,Accounts Payable Services ; Lubczynski,Artur,PL-Warszawa,IT Finance & Legal ; Cialdella,Marcelo,ES-Esplugues Llobregat ; Pinchuk,Oleksandr,UA-Lviv,Accounts Payable Services ; Rotar,Sofiia,UA-Lviv,Accounts Payable Services
Subject: [EXTERNAL] Request for Support on Tax ID Verification Solutions

Dear Julie,
I hope this message finds you well.
I am reaching out to seek your assistance in identifying potential solutions for verifying Tax IDs. Our primary objective is to prevent any discrepancies between the data presented on invoices and what is recorded in the SAP system.
We require these checks for both our entities and the suppliers' entities.
Nestlé Tax ID Concerns: I have identified a risk where IS suppliers may upload records from their ERP systems, which could allow for manipulation of Nestlé's name, address, and Tax ID. While they provide our AAA number, other data may differ.
Supplier Tax ID Issues: The E-invoicing Team is currently assigning our internal vendor codes to Tungsten accounts; however, all data on the suppliers' accounts remains editable. This raises the potential for mismatches.
Your insights and recommendations on how we can address these issues would be greatly appreciated.
Thank you for your support.
Julia
46Billing reconciliation report request to send weeklyGlobalBilling reconciliation report request to send weeklyNestlé01.09.2025MediumIn ProgressRayén/reporting21/10/2025: reporting in progress.to share first draft this week and then compare november reports
07/10/2025: in progress. To compare to September data when available.
23/09/2025: Rayen to check internally status
47Secondary vendor codeGlobalSecondary vendor codeNestlé11.09.2025MediumCompleteNestléTested, worked.
23/09/2025: Nestle to test

Speak to one of our experts

You have unique challenges and requirements. Arrange a call to find out how we can help automate your specific processes.

Get in touch